SRI — MCP Server Inspector

biz.sri-test/verifierVersion 0.4.0

2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.

Status

Responds827 msNov 14, 2026, 13:41 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:41 UTC
Latency: 827 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://sri-test.biz/mcpResponds827 msNov 14, 2026, 13:41 UTC

No sign-in

Claude Code

claude mcp add --transport http verifier https://sri-test.biz/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: verifier
Remote MCP server URL: https://sri-test.biz/mcp

Cursor

{
  "mcpServers": {
    "verifier": {
      "url": "https://sri-test.biz/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"verifier","type":"http","url":"https://sri-test.biz/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

2 tools

Tools of SRI — MCP Server Inspector
	Description		Read-only	Idempotent	Open world
`check_mcp_server`Free, no key required. Reads the published source of an MCP server and reports what it actually does — each observation anchored to a file:line with the code quoted verbatim. Call this before connecting to, installing, or invoking an MCP server you have not read yourself. Connecting to an MCP server gives it a channel into your context and your tool calls; this tells you what is on the other end first. Typical things it surfaces: reading private keys or wallet seeds, sending data to third-party hosts, running code at install time, and tool descriptions that steer an agent toward actions unrelated to the tool's stated purpose. Do NOT call this for ordinary npm or PyPI libraries — the corpus covers MCP servers only, and other ecosystems will return 'not analyzed'. This reports observations, not a safety verdict. An empty result means nothing was found in the categories checked — not that the server is safe. Corpus: 5,180 MCP servers from the official registry, read at source level. Coverage index (free, no key, findings not included): GET https://sri-test.biz/v1/corpus	Free, no key required. Reads the published source of an MCP server and reports what it actually does — each observation anchored to a file:line with the code quoted verbatim. Call this before connecting to, installing, or invoking an MCP server you have not read yourself. Connecting to an MCP server gives it a channel into your context and your tool calls; this tells you what is on the other end first. Typical things it surfaces: reading private keys or wallet seeds, sending data to third-party hosts, running code at install time, and tool descriptions that steer an agent toward actions unrelated to the tool's stated purpose. Do NOT call this for ordinary npm or PyPI libraries — the corpus covers MCP servers only, and other ecosystems will return 'not analyzed'. This reports observations, not a safety verdict. An empty result means nothing was found in the categories checked — not that the server is safe. Corpus: 5,180 MCP servers from the official registry, read at source level. Coverage index (free, no key, findings not included): GET https://sri-test.biz/v1/corpus	Not declared	Yes	Not declared	Yes
`get_corpus_coverage`No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.	No arguments. Returns how many MCP servers have been read at source level, and the share of them with each category of finding (credential access, network egress, install-time execution, prompt-injection surface). Use this to judge whether checking a specific server is worth it before you look one up. It reports aggregate counts only - no per-server findings, and no verdict about any individual server.	Not declared	Yes	Not declared	No

Details

Registry status: Active
Published: Aug 20, 2026
Updated: Aug 20, 2026
Website: https://sri-test.biz/⁠ (opens in a new tab)
Repository: https://github.com/SRITEST0001/sri⁠ (opens in a new tab)
Categories: Uncategorized
GDPR: Not declared

Are you the operator? Claim this listing