Skip to main content

Platform capability · Boundary and evaluation, one plan

ECZ-ID Intent + Intent Control

Both services in one plan: the authorised boundary and its runtime control.

  • Paid · Open

ECZ-ID Intent + Intent Control puts the two services in one plan. Intent records what an identity is authorised to do — its objective, its constraints and its validity — as authorised by an owner or administrator of your organisation. Intent Control evaluates a proposed action against that authority, the Intent, your policy and optional counterparty context, and records the decision with its basis. A decision is EVALUATED unless an inline enforcement point reports mediating it; payment authorises nothing.

For an MCP server: For an MCP server: state what its tools may act on, then evaluate each proposed tool call against that boundary and your policy before the call is made.

The same products and entitlements serve all seven Passport families. There is no MCP edition — only MCP examples.

Buy monthly — ECZ-ID Intent + Intent Control (continues on trustops.ecocitizenz.com)All tiers, prices and availabilityAll MCP products

Every Intent + Intent Control plan in TrustOps (continues on trustops.ecocitizenz.com)

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

Platform capability

Why it matters for MCP servers and tools

An MCP server's tools act. The combined plan gives the server a written, owner-authorised boundary and a recorded decision for each proposed tool call against it.

The decision is EVALUATED: enforcement stays with the runtime, gateway or client that mediates the call, outside the ECZ-ID layer.

ECZ-ID Intent + Intent Control: fit, outcomes and contents

Best for

  • MCP providers that want to state what a server's tools may do and have proposed tool calls evaluated against it.
  • Platform teams that would otherwise buy Intent and Intent Control separately for the same protected entities.
  • Organisations preparing an enterprise-managed authorization design, where the boundary and its evaluation belong together.

What you get out of it

  • An owner-authorised statement of objective, constraints and validity for each covered identity.
  • A recorded, EVALUATED decision for each proposed action, with its basis.
  • One plan and one cadence for both, managed from your ECZ-ID account.

What is included

  • Intent: covered places for authorised Intents, set by the tier.
  • Intent Control: protected entities, hosted decisions and policy syncs for runtime control, set by the tier.
  • Evaluation against authority, the Intent, policy and optional counterparty context.
  • The same product across all seven Passport families.

How it works

  1. An owner or administrator authorises the Intent for an identity: objective, constraints and validity.

  2. Before acting, a caller submits the proposed action for evaluation.

  3. Intent Control returns a decision with its basis, recorded as EVALUATED.

  4. Your runtime, gateway or enforcement point decides whether to act on it; only an inline enforcement point that reports mediating the action makes it ENFORCED.

Use cases

MCP jobs Intent + Intent Control serves

What it is not

  • Payment authorises nothing: an Intent is authorised only by an owner or administrator, and a Passport is not an Intent authorisation.
  • A decision is EVALUATED, never ENFORCED, unless an inline enforcement point reports mediating the action.
  • Coverage is not AEC capacity; the two are counted separately. One active plan per service.

Professional services it pairs with

Tiers, prices and availability

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

No VAT is charged: the published price is the full price, and nothing is added at TrustOps checkout.

Related

Related MCP products

Proof & evidence

Resolve before reliance

  • The Resolver is the live public proof: anyone re-checks a record there, with no account.
  • The machine-readable record is a deterministic projection of the same record, for tools and agents.
  • A badge or a QR code is a route back to the live proof, never proof on its own.

Verify an ECZ-ID (opens in a new tab — resolver.ecocitizenz.org)

Developer route

The Developer Gateway defines the technical contracts — schemas, fields and result vocabularies — for Intent + Intent Control. This site links them and never restates them.

FAQ

Questions about Intent + Intent Control

What does Intent + Intent Control not do?

Payment authorises nothing: an Intent is authorised only by an owner or administrator, and a Passport is not an Intent authorisation. A decision is EVALUATED, never ENFORCED, unless an inline enforcement point reports mediating the action. Coverage is not AEC capacity; the two are counted separately. One active plan per service.

Where are the prices, and how do I start?

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. Each row on this page links to its own TrustOps destination, with its cadence or edition already chosen.

How do I manage Intent + Intent Control once I have it?

Sign in to TrustOps and manage it from your ECZ-ID account. TrustOps holds the order, the entitlement and any renewal; this site never does.

How does someone re-check the MCP server it relates to?

Resolve before reliance. The Resolver is the live public proof; the machine-readable record is a deterministic projection of the same record; a badge or QR code is a route back to it. No product on this page becomes proof itself.

Price and availability

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

  • Paid · Open
Buy monthly — ECZ-ID Intent + Intent Control (continues on trustops.ecocitizenz.com)Get a FREE MCP Passport (continues on trustops.ecocitizenz.com)

Keep going

Where next on ECZ-ID MCP

Create free MCP Passport (continues on trustops.ecocitizenz.com)