SRI

Endpoints (3 live)

• POST /v1/x402/verify — Read what an MCP server does before connecting: findings quoted at file:line from its published source. POST {ecosystem:'mcp', name, version}. Charged only when an analyzed result is returned. (0.2 USDC on Base)
• GET /v1/x402/verify — Read what an MCP server does before connecting: findings quoted at file:line from its published source. POST {ecosystem:'mcp', name, version}. Charged only when an analyzed result is returned. (0.2 USDC on Base)
• HEAD /v1/x402/verify — Read what an MCP server does before connecting: findings quoted at file:line from its published source. POST {ecosystem:'mcp', name, version}. Charged only when an analyzed result is returned. (0.2 USDC on Base)

MCP tools (2)

SRI — MCP Server Inspector https://sri-test.biz/mcp

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