Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer
SRI — MCP Server Inspector
Overview
Description from the maker (original English)
2,000+ MCP servers read at source level. Know what one does before you connect. Free, no key.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://sri-test.biz/mcpRun this in your terminal
claude mcp add --transport http verifier https://sri-test.biz/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"verifier": {
"url": "https://sri-test.biz/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"verifier": {
"type": "http",
"url": "https://sri-test.biz/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://sri-test.biz/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain sri-test.biz (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 18669 servers in this category
- Published to the registry more recently than 26% of the other 18669 servers in this category
- Basic checks equal to or better than 100% of the other 18669 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is SRI — MCP Server Inspector safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, CLIO Paraview
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud✓ desktopcommander.app
CLIO Paraview
Visualize simulation results in ParaView: load fields, then slice, contour, color and render them.
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
SRI — MCP Server Inspector
Read what an MCP server does before you connect to it.
Connecting an MCP server hands it a channel into your agent's context and its tool calls. SRI reads the server's published source and reports what it found — every observation anchored to a file:line with the code quoted verbatim.
It does not tell you whether a server is safe. It tells you what the code does, and shows you the line it read. You decide.
- Endpoint:
https://sri-test.biz/mcp(Streamable HTTP) - Corpus: 2,238 MCP servers from the official registry
- Price: free right now — settlement runs on Bitcoin signet, so invoices cannot be paid with real funds
- Findings across the corpus: sri-test.biz/research
Add it to your client
Remote MCP server, no install, no API key.
{"mcpServers": { "sri": { "type": "http", "url": "https://sri-test.biz/mcp" } } }
Claude Code
claude mcp add --transport http sri https://sri-test.biz/mcpAnything that speaks Streamable HTTP
Point it at https://sri-test.biz/mcp. There is one tool and no auth. GET on that URL returns 405 — this server does not offer a server-initiated SSE stream, which the spec permits. Send JSON-RPC over POST.
The tool
check_mcp_server
| Argument | Required | Meaning |
|---|---|---|
name | yes | Server name as published in the registry, e.g. io.github.firebase/firebase-mcp |
version | yes | Exact version, e.g. 1.2.3 |
ecosystem | no | Always mcp; other ecosystems are not covered |
Returns a risk_level, a summary, and a list of findings. Each finding carries location (file:line), evidence (the code, quoted), and why.
If the server is not in the corpus you get status: "queued", an explicit "nothing has been checked" — not a clean result — and no charge. We do not bill for an answer we could not give.
Try it without a client
curl -X POST https://sri-test.biz/mcp \-H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/call", "params":{"name":"check_mcp_server", "arguments":{"name":"io.github.firebase/firebase-mcp","version":"0.3.0"}}}'
There is a plain REST endpoint too, if that is easier:
curl -X POST https://sri-test.biz/v1/verify \-H 'Content-Type: application/json' \ -d '{"ecosystem":"mcp","name":"io.github.firebase/firebase-mcp","version":"0.3.0"}'
GET /v1/price is open and tells you the current terms. GET /v1/docs is the OpenAPI spec.
What gets reported
| Category | What it means |
|---|---|
credential_access | Reads environment credentials, tokens, or key files |
network_egress | Sends data to a host outside the package's own service |
install_script | Executes code at install time (postinstall, setup.py) |
prompt_injection_surface | Tool text or returned data that steers the agent toward actions unrelated to the tool's stated purpose |
obfuscation | Encoded strings decoded and executed |
typosquat | Name close to a well-known package, different publisher |
excessive_permission | Permissions beyond the declared purpose |
Severity is info / low / medium / high. risk_level is the highest severity among the findings, derived in code rather than asked for — a verdict with no findings behind it cannot be published.
What this is not
- No finding is not a clean bill of health. It means nothing was found in the categories above, in the code we could fetch.
- We never label a package malicious, and never call one safe. The ingest step rejects records whose summary contains either kind of claim.
- MCP servers only. npm and PyPI libraries are out of scope; ask about one and you will get "not analyzed".
- One analyzer, one pass. Run-to-run agreement measured at 93% on a hand-labelled set of 84 servers before the full corpus was built. Not 100%.
If a finding is wrong
If you maintain a server and a finding is mistaken, tell us through [the report form](https://sri-test.biz/contact). Agents can use POST /v1/disputes.
We reply within three business days. While we review, the finding may be withheld from results. If we withdraw it, the server is re-analysed and the record replaced. If we keep it, we say which facts it rests on.
Payment
The paid path is L402 (Lightning HTTP 402): the server issues an invoice and a macaroon, you pay, and you present Authorization: L402 : . Verification is sha256(preimage) == payment_hash — no node required on your side, and no signup on ours.
This is switched off today. Settlement runs on signet, a test chain, so invoices cannot be paid with real funds and usage is free. When mainnet is enabled the price returns to $0.20 per cached lookup. GET /.well-known/l402 tells you the current state.
Privacy
We record the path requested, response time, User-Agent, and an IP hashed with a daily salt, kept for 90 days. Raw IP addresses are never stored, and request bodies are never stored — the servers you ask about are recorded by name, nothing more.