DID.is evidence

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

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

7 tools

• 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 server.

• 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.

Security scan

Recent checks