Skip to content
Did logo

Did MCP server

Which MCP servers are Did'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-10-28

← Back to Did

Whose server it is
  • Registry nameis.did/mcpverified in the MCP registry

The registry name sits under did.is. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools7
  • Server calls itselfDID.is
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 217 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check whether a DID resolves to verifiable keys; inspect MCP servers and A2A agent cards before use; verify credentials and their status lists.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "check whether a DID resolves to verifiable keys", the likely first call is resolve_did.
  • For "inspect MCP servers and A2A agent cards before use", the likely first call is inspect_mcp_server.
  • For "verify credentials and their status lists", the likely first call is verify_credential.
  • Parameters are untyped or undescribed in 4 of 7 tools: check arguments before calling.

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 dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer288 ms
  • Space in an agent's context≈ 1,000 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 7

What an agent can do with it

  • can do · check whether a DID resolves to verifiable keys
  • can do · inspect MCP servers and A2A agent cards before use
  • can do · verify credentials and their status lists

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

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 →

Tools it offers7 tools · read 2026-10-28
  • resolve_did

    Resolve a DID (did:key, did:jwk, did:web, did:webvh) and report which evidence dimensions are established and which are not. Read-only; fetches the DID document from its origin.

  • verify_credential

    Verify a W3C Verifiable Credential or SD-JWT VC (JSON object or compact string): signature, validity period and status list. Optional requiredClaims checks issuer-signed claim values. Read-only.

  • inspect_mcp_server

    Inspect a remote MCP server over Streamable HTTP: protocol version, tool inventory fingerprints, declared annotations versus DID.is side-effect heuristics, and changes since the last observation. Read-only; never authenticates to the…

  • inspect_a2a_agent

    Fetch an A2A agent card (agent URL or card URL) and report its signature status, interfaces and skills. Read-only.

  • authorize_tool_call

    Check whether a DID.is delegation chain (compact JWTs, root first) allows an agent to call a given tool. Returns ALLOW or DENY with the verified chain. Read-only; nothing is stored.

  • evaluate_policy

    Evaluate a DID against declarative rules (allowed methods, curves, domain binding, TLS, linked accounts, verifiable history, credential status). Returns PASS, FAIL or INDETERMINATE (not a pass). Read-only.

  • search_directory

    Search the public DID.is directory of DIDs whose controllers proved control and chose to be listed. Matches names and domains. Read-only.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "did": {
      "type": "http",
      "url": "https://did.is/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http did https://did.is/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://did.is/mcp as a custom connector in the settings.

OpenAPI spec

20 paths, read 2026-10-28. 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.