Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer
X402score MCP
Overview
Description from the maker (original English)
Check an x402-paid API endpoint's trust score before paying it - live-probed, not self-reported.
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↓ 52/wk · ★ –
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 on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"x402score": {
"command": "npx",
"args": [
"-y",
"x402score-mcp"
]
}
}
}Run this in your terminal
claude mcp add x402score -- npx -y x402score-mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"x402score": {
"command": "npx",
"args": [
"-y",
"x402score-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": {
"x402score": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"x402score-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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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
Runs on your computer; the tool list appears in your AI app after you install it.
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 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account zagchk, which owns the repo
- … 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 applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18444 servers in this category
- Published to the registry more recently than 68% of the other 18444 servers in this category
- Basic checks equal to or better than 100% of the other 18444 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 X402score MCP 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 on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.2) reached the registry 20 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Tethered Trust
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
Tethered Trust
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Runs in the cloud✓ tetheredtrust.com
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.
x402score-mcp
MCP server exposing x402Score's reputation data as agent tools — check an x402-paid API endpoint's trust score before paying it, from inside any MCP-compatible client (Claude Desktop, Claude Code, etc.).
Published to npm, not yet submitted to any MCP registry. The package itself (x402score-mcp) is installable now — what's being held is the *registry listing* (Claude's, Smithery, etc.), until the on-chain modifier's calibration gate closes (~2026-10-19); see the main project README for why. Registry listing content is pre-written in REGISTRY_SUBMISSION.md, ready to copy-paste the moment the gate closes. Last re-verified end-to-end against live production (real stdio MCP client, all 5 tools + the methodology resource, confirmed structured output, error handling, and tool annotations all work correctly): 2026-10-10.
Tools
- `check_endpoint_score` — score, grade, and credible interval for one endpoint. Pass
urldirectly (preferred — the endpointId is derived locally, no separate lookup) orendpointIdif already known. - `search_leaderboard` — search/browse tracked endpoints by name/domain/url/id and/or vertical, sortable by
score(default),price,uptime, orlatency. - `get_calibration_report` — is the scoring formula actually predictive?
- `submit_endpoint` — add a new x402 endpoint to the monitoring queue.
- `ping` — cheap reachability/latency check, useful as a first call when connecting.
All tools declare readOnlyHint/destructiveHint/idempotentHint/openWorldHint annotations and a matching outputSchema, and all return structured errors (isError: true with a clear message, including the backend's own error text where available — e.g. a rate-limit message, not just an HTTP status) instead of letting a network failure or backend timeout kill the connection. A x402score://methodology resource explains what the score, grade, credible interval, and on-chain modifier actually mean — read once per session rather than inferred from tool descriptions alone. Requests time out client-side after 10s so a slow or degraded backend fails fast and visibly instead of hanging the caller. See CHANGELOG.md for the version history.
Install & run
npm install -g x402score-mcpx402score-mcp
Or from source:
cd mcp && npm install && npm run buildnpm start
Use from Claude Desktop / Claude Code
Add to your MCP client config:
{"mcpServers": { "x402score": { "command": "npx", "args": ["-y", "x402score-mcp"] } } }
Or point command/args at a local node/dist/server.js build instead, same as before.
Optionally set X402SCORE_BASE_URL in the server's env to point at a local wrangler dev or staging deployment instead of production. This redirects *all* of the server's traffic to whatever URL you give it, so only set it to a backend you control and trust.
Development
Tool logic (src/tools.ts) is separated from MCP protocol wiring (src/server.ts) specifically so it's testable without a real MCP transport — tests run via the main project's vitest (from the repo root: npm test). src/server.ts wires those same functions into @modelcontextprotocol/sdk's McpServer, connected over stdio.