SRI — MCP Server Inspector

by sri-test Your server? Claim it

answering

SRI — MCP Server Inspector is answering right now. Last checked 12 min ago. It exposes 2 tools. Last commit 20 Aug 2026.

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

Uptime history 13 days of history · worst day 98%

13 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

946 ms

Response time

average over 24h

Stars

last commit 20 Aug 2026

Nothing serious here today

Today is the operative word: we check SRI — MCP Server Inspector every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.verifier]
url = "https://sri-test.biz/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

corpus

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.

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: 2,781 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

Endpoints

URL	Transport	State	Latency	Checked
https://sri-test.biz/mcp	streamable-http	answering	908 ms	12 min ago

Alternatives to SRI — MCP Server Inspector

same job, measured the same way

Mintqa MCP

by adamgusky

MCP server for Mint — AI-powered QA that runs your app in a real browser on every PR.

31 installs/wk answering

Micropay Test Suite

by netlify-micropay-test-suite

Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.

1 tools answering

Appstore Connect

by sardorbekr

MCP server for Apple's App Store Connect API. Manage apps, TestFlight, and more.

89 installs/wk local only

MCP Compliance

by yawlabs

CLI tool and MCP server that tests MCP servers for spec compliance

703 installs/wk local only

Testing Repo

by vinur1992

An MCP server that created for demo

local only

LiveVariant

by livevariant

Build, inspect and read adaptive A/B tests. Config travels in the URL; no account or API key needed.

863 installs/wk 9 tools answering

Roslyn CodeLens

by marcelroozekrans

Roslyn MCP server: semantic .NET/C# intelligence - analysis, refactoring, tests, IL inspection.

197 installs/wk local only

xmp4 — Semantic code knowledge for your stack

by example4

OSS libs in your stack, really used: source, tests, callers. C#, Java, TS, Python, Rust, PHP+.

16 tools answering

SRI — MCP Server Inspector — questions

Answers built from our own checks of this server.

What can SRI — MCP Server Inspector do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_mcp_server, get_corpus_coverage. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is SRI — MCP Server Inspector working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 946 ms. The bar chart above shows every period we have measured.

How do I connect SRI — MCP Server Inspector?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SRI — MCP Server Inspector need an API key?

No. SRI — MCP Server Inspector completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is SRI — MCP Server Inspector?

It answers our handshake in 946 ms on average, which is faster than 11% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is SRI — MCP Server Inspector open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.