mcpbeat Sign in

DID.is evidence MCP Server

by did Your server? Claim it
answering

DID.is evidence is answering right now. Last checked 11 min ago. It exposes 7 tools.

Read-only checks for DIDs, credentials, MCP servers, A2A cards and agent delegation.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
509 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check DID.is evidence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://did.is/mcp
Settings → Connectors → Add custom connector, then paste this address
https://did.is/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://did.is/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://did.is/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://did.is/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inspect
inspect_a2a_agent
Fetch an A2A agent card (agent URL or card URL) and report its signature status, interfaces and skills. 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 server.
authorize
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.
directory
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.
evaluate
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.
resolve
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
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.

Endpoints

URLTransportStateLatencyChecked
https://did.is/mcp streamable-http answering 439 ms 11 min ago

Alternatives to DID.is evidence

same job, measured the same way
T
TestedMCP
by testedmcp

Read-only lookup of tested agent tools and MCP servers: scores, test evidence, deprecation.

4 tools answering
agentgate
by ciceroyang

Read-only evidence for the tools agents run: MCP server records, coverage and policy.

39 installs/wk local only
A
AgentAuth
by raditotev

Identity and auth for AI agents: credentials, tokens, delegations, and permission checks.

138 installs/wk local only
Docs MCP
by acta-team

Read-only MCP server for the official ACTA verifiable credentials documentation.

27 installs/wk local only
Ccs
by correctover

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

local only
Autron Core
by hungnguyenhtbvn-max

Open Identity Standard for AI Agents — DID, Agent Cards, delegation, reputation, payment & escrow

29 installs/wk local only
MCP Abap Adt Sse Ro
by fr0ster

Read-only MCP server for SAP ABAP ADT over HTTP+SSE: x-sap-* header credentials

227 installs/wk local only
HODLXXI Read-Only
by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering

DID.is evidence — questions

Answers built from our own checks of this server.

What can DID.is evidence do?
It exposes 7 tools, read directly from the server on our last check. Among them: authorize_tool_call, evaluate_policy, inspect_a2a_agent, inspect_mcp_server, resolve_did, search_directory and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is DID.is evidence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 509 ms. The bar chart above shows every period we have measured.
How do I connect DID.is evidence?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does DID.is evidence need an API key?
No. DID.is evidence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is DID.is evidence?
It answers our handshake in 509 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.