Scale
AEC — Active Entity Capacity
- Paid · Open
- By arrangement · Enquiry
Scale the estate you actively operate without turning capacity into identity.
For an MCP server: An MCP server you actively manage in production, with live bindings and current state, counts as one active entity — in the same pool as your agents, APIs and other identities.
AEC is capacity, not verification, certification or trust status.
Current state
PulseGuard
- Paid · Open
- By arrangement · Enquiry
Know the current state of the ECZ-ID entities you operate.
For an MCP server: For an MCP server: its record's lifecycle and binding state evaluated on demand, with the basis shown, so an operator sees which servers need attention before a customer's re-check does.
PulseGuard reports observed state; it is not a safety verdict or certification.
Evidence
LedgerCore
- Paid · Open
- By arrangement · Enquiry
Keep decisive identity and lifecycle evidence without pretending evidence proves the claim inside it.
For an MCP server: For an MCP server: when its binding or operator changes, the lifecycle event is kept with its time, so a customer's reviewer can see what was recorded and when.
A record shows what was recorded and when; it does not make the statement true.
Relationships
ECZ-ID Graph Intelligence
- Paid · Open
- By arrangement · Enquiry
See the relationships that make a machine-economy identity meaningful.
For an MCP server: For an MCP server: the path from the server to its operator, the agents that call it, the API behind it and the package that ships it — each a distinct identity.
A Graph relationship is a published relationship, not an endorsement.
Change awareness
ECZ-ID Watch
- Free · Open
- Paid · Open
- By arrangement · Enquiry
Know when public ECZ-ID information you rely on has changed.
For an MCP server: For a team whose agents rely on third-party MCP servers: follow each server's ECZ-ID, see what changed, and re-check the Resolver when its operator, binding or state has changed.
A Watch notification is a change signal, not certification, approval or a safety assessment.
Retained receipts
ECZ-ID Receipts
Keep the receipts your ECZ-ID activity produces, retained in your Receipts Vault and searchable.
For an MCP server: For an MCP server: keep the receipts its ECZ-ID activity produced, so a customer's reviewer can see what was recorded about the server, and when.
Paying for Receipts buys retention: an allowance for your organisation's Receipts Vault. It never makes a receipt valid, verified, anchored or signed.
Authorised objective
ECZ-ID Intent
Define the authorised objective, constraints and validity of what a Passport may do.
For an MCP server: For an MCP server: record the objective and the constraints its tools may act within, authorised by your organisation's owner or administrator.
Payment is not authorisation: an Intent is authorised only by an owner or administrator.
Action evaluation
ECZ-ID Intent Control
Evaluate a proposed action against authority, the Intent, policy and optional counterparty context.
For an MCP server: For an MCP server: evaluate a proposed tool call against the server's Intent and your policy before the call is made, and keep the EVALUATED decision.
A decision is EVALUATED, never ENFORCED, unless an inline enforcement point reports mediating the action.
Boundary and evaluation, one plan
ECZ-ID Intent + Intent Control
Both services in one plan: the authorised boundary and its runtime control.
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.
Payment authorises nothing: an Intent is authorised only by an owner or administrator, and a Passport is not an Intent authorisation.