MCP server check
Paste the Streamable HTTP endpoint of a public MCP server. DID.is lists its tools, fingerprints every definition, flags risky descriptions and tells you what changed since the last check — then gives you a README badge.
DID.is speaks Streamable HTTP: server/discover (MCP 2026-07-28, stateless) with a fallback to the legacy initialize session handshake. It never authenticates to third-party servers. The last result of a public check is stored and shown to anyone who checks or looks up the same endpoint (tool count, whether tool definitions changed, and the date). Inspection history also retains the endpoint, timestamps, tool names and definition/schema fingerprints for drift comparison.
What the check proves, and what it does not
It proves which tools the server listed at the time of the check and whether their definitions changed since DID.is last saw them. Side-effect classes and risk signals are heuristics over the server's own text, not an audit of its code.
Servers that require sign-in are reported as such; DID.is never authenticates to third-party servers.
The last result of a public check is stored and shown to anyone who checks or looks up the same endpoint (tool count, whether tool definitions changed, and the date). Inspection history also retains the endpoint, timestamps, tool names and definition/schema fingerprints for drift comparison.
Search the official MCP Registry by server name on public MCP servers to see DID.is's last stored public check for each endpoint.
Automate it with GET /api/v1/mcp/inspect — see the developer reference or the full agent trust workbench.