
Certisyn MCP server
Which MCP servers are Certisyn's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-11-13
- Registry namecom.certisyn/verifyverified in the MCP registry
The registry name sits under certisyn.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-11-13
- Tools9
- Server calls itselfcertisyn
- Server version1.0.0
- Protocol version2025-06-18
On 2026-11-13 the server answered initialize and tools/list without a sign-in. First answer in 337 ms.
Should an agent connect it
- On Nov 20, 2026 we called its read-only tools following a fixed scenario, and 1 of 1 steps returned what the check expects.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
Measured daily
- INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
- Checked by calling it1 of 1 steps passedlatest run Nov 20, 2026, read-only calls only
- Answered100% of days9 of 9 daily checks
- Median first answer323 ms
- Space in an agent's context≈ 1,302 tokensthe definitions of all its tools (9), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
verification_capabilitydescribed by the serverReturns what Certisyn can and cannot verify today, with the coverage fraction and the claim types no domain covers. Read this before promising a user that something is verifiable.
resolve_determinationdescribed by the serverResolve the code printed on a Certisyn badge or certificate to its determination: state, policy version, claim summary by state, the sealed root and its public anchor. An unknown code is not a negative finding; treat it as undetermined.
resolve_attestationdescribed by the serverResolve a counterparty attestation code to the attestation it names and the partner that issued it.
verify_mandatedescribed by the serverBefore you accept an act from an agent that says it acts for someone else, resolve the mandate code it presented. Pass agent_ref (the identifier the agent presented), action (family.verb, for example payment.initiate) and, where they…
verify_anchordescribed by the serverIndependently verify an anchored evidence root. With leaf_hash, also returns the inclusion proof so the caller can recompute it without trusting Certisyn. An unknown root is not anchored, never verified.
registry_searchverified Nov 20, 2026Confirm a subject you already hold a name for. This is a resolver, not a directory: it returns only subjects that chose to be discoverable, so absence is never a finding.
bastion_verify_credentialdescribed by the serverPublicly verify a Bastion posture credential for a target domain or by credential id, without an account.
compliance_snapshotdescribed by the serverFetch the sealed snapshot of anchored verification records for a named compliance period, as a regulator would. Deterministic for a sealed period.
consilience_verifydescribed by the serverCheck whether a media artefact is physically consistent with the place and time it is claimed to have been captured. Payload size is capped and calls are throttled.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"verify": {
"type": "http",
"url": "https://app.certisyn.com/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http certisyn https://app.certisyn.com/api/mcpclaude.ai, ChatGPT and other clients: add https://app.certisyn.com/api/mcp as a custom connector in the settings.
OpenAPI spec
7 paths, read 2026-11-13. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.