Runnable MCP examples: inspect public servers and block wrapped calls when appro
Runnable MCP examples: inspect public servers and block wrapped calls when approved tool definitions change.
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://did.is/mcp |
|---|---|
| Source | https://github.com/did-is/mcp-examples |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-11-03 22:09:14 |
| Last checked | 2026-11-17 21:48:45 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 568 / 820 ms |
| Last successful check | 2026-11-17 21:48:45 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
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; fetcverify_credential— Verify a W3C Verifiable Credential or SD-JWT VC (JSON object or compact string): signature, validity period and status list. Optional requirinspect_mcp_server— Inspect a remote MCP server over Streamable HTTP: protocol version, tool inventory fingerprints, declared annotations versus DID.is side-effinspect_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 verievaluate_policy— Evaluate a DID against inline declarative rules or a saved team policyRef (allowed methods, curves, domain binding, TLS, linked accounts, vesearch_directory— Search the public DID.is directory of DIDs whose controllers proved control and chose to be listed. Matches names and domains. Read-only.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:48:45 | ✓ | ✓ | 831 ms | 90 | active |
| 2026-11-17 21:33:39 | ✓ | ✓ | 767 ms | 90 | active |
| 2026-11-17 21:18:26 | ✓ | ✓ | 681 ms | 90 | active |
| 2026-11-17 21:03:22 | ✓ | ✓ | 547 ms | 90 | active |
| 2026-11-17 20:48:02 | ✓ | ✓ | 820 ms | 90 | active |
| 2026-11-17 20:32:56 | ✓ | ✓ | 697 ms | 90 | active |
| 2026-11-17 20:17:54 | ✓ | ✓ | 633 ms | 90 | active |
| 2026-11-17 20:02:19 | ✓ | ✓ | 480 ms | 90 | active |
| 2026-11-17 19:46:57 | ✓ | ✓ | 766 ms | 90 | active |
| 2026-11-17 19:31:54 | ✓ | ✓ | 726 ms | 90 | active |
| 2026-11-17 19:16:47 | ✓ | ✓ | 538 ms | 90 | active |
| 2026-11-17 19:01:04 | ✓ | ✓ | 869 ms | 90 | active |
| 2026-11-17 18:46:01 | ✓ | ✓ | 761 ms | 90 | active |
| 2026-11-17 18:30:59 | ✓ | ✓ | 625 ms | 90 | active |
| 2026-11-17 18:15:56 | ✓ | ✓ | 664 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://did.is/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/did-is-mcp # JSON