Developer tool · Free tool · Resolver-posture checker
ECZ-ID MCP Verifier™
Check an MCP server's public resolver posture before a high-risk tool call.
- Free · Open
The ECZ-ID MCP Verifier is a free, machine-readable checker for MCP servers, tools and agent manifests. It reads a target's declared ECZ-ID manifest and the public Resolver, and returns one canonical result state with its reason codes. It reads current Resolver posture, creates nothing and proves nothing on its own: your local policy decides what to do with the result.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
Developer tool
Why it matters for MCP servers and tools
An agent can be pointed at any MCP server. The Verifier lets the platform re-check, from public surfaces, who operates the server before a high-risk tool call — without anyone on this site or at EcoCitizenz deciding for it.
The result vocabulary and the policy examples live on the Developer Gateway, which owns them; this page routes there rather than copying them.
ECZ-ID MCP Verifier™: fit, outcomes and contents
Best for
- Platforms and agents that call MCP tools and want a re-check before a high-risk call.
- CI pipelines that should notice when a server's public posture changes.
- Enterprises writing an allow / warn / require policy over the MCP servers they permit.
What you get out of it
- One canonical result state per target, with reason codes, from public surfaces only.
- A re-check you can run in your terminal, your CI or your agent.
- A clear line between absence of public proof and a problem: absence is reported as absence.
What is included
- Free to use: nothing to buy and no account.
- A CLI, a stdio MCP server and a GitHub Action, each set out on this site's Developers page.
- Reads only the public manifest and Resolver surfaces; no secrets are needed.
How it works
Point the Verifier at an MCP server, tool or agent manifest.
It reads the declared manifest and resolves the declared parent ECZ-ID and bindings against the public Resolver.
It returns a canonical result state and reason codes; it never infers safety or approval.
Your local policy — allow, warn or require — decides what happens next.
Use cases
MCP jobs MCP Verifier serves
- Decide which MCP servers your organisation allowsTeams connect agents to MCP servers faster than a review board can keep up, and an allow-list built from names and URLs drifts as servers change hands, endpoints and tools.The steps and what serves each
- Pre-check a high-risk tool call before an agent makes itAn agent calls whatever tool it is pointed at. By the time anyone reads the log, the call has happened, and nobody re-checked who operates the server that exposed the tool.The steps and what serves each
What it is not
- The Verifier does not change canonical state, mark anything bound or activate proof; the Resolver stays the public proof surface.
- No public resolver proof found yet does not mean unsafe. Re-check before reliance.
- It never promises that a server is safe, vetted or approved, and it is not open source.
Professional services it pairs with
MCP Readiness Audit
£395
- Paid in full at checkout
Enterprise MCP Pilot
£6,500 total
- One-off engagement, paid in stages
- £2,600 due now, then 2 later milestones
Tiers, prices and availability
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
ECZ-ID MCP Verifier™
Free machine-readable checker for MCP servers, tools, and agent manifests. Use it before any high-risk tool call.
Free
No VAT is charged: the published price is the full price, and nothing is added at TrustOps checkout.
Related
Related MCP products
- MCP assurance planECZ-ID MCP Assurance plansTrack the binding state, tool-list fingerprint and drift of the production MCP servers you operate, with an exportable evidence pack.Its page
- Platform capabilityECZ-ID WatchKnow when public ECZ-ID information you rely on has changed.Its page
- Platform capabilityECZ-ID Graph IntelligenceSee the relationships that make a machine-economy identity meaningful.Its page
- Platform capabilityECZ-ID IntentDefine the authorised objective, constraints and validity of what a Passport may do.Its page
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 MCP Verifier. This site links them and never restates them.
FAQ
Questions about MCP Verifier
What does MCP Verifier not do?
The Verifier does not change canonical state, mark anything bound or activate proof; the Resolver stays the public proof surface. No public resolver proof found yet does not mean unsafe. Re-check before reliance. It never promises that a server is safe, vetted or approved, and it is not open source.
Does MCP Verifier cost anything?
No. It is free to use, with no paid checkout and no account, and it creates nothing on its own.
How do I manage it?
There is nothing to manage on this site: the tool runs where you install it. Any ECZ-ID you hold is managed from your ECZ-ID account.
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.
- Free · Open
Keep going
Where next on ECZ-ID MCP
Create free MCP Passport (continues on trustops.ecocitizenz.com)- Free MCP Passport Free · Permanent · No card. One logical MCP server, one Passport.
- Every MCP product Each with its own page and its exact TrustOps destination.
- MCP use cases Publish, allow-list, pre-check a tool call, migrate — and what serves each.
- Verify an ECZ-ID Resolve before reliance, on the live public Resolver. (opens in a new tab — resolver.ecocitizenz.org)