Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Stdio MCP proxy: free probe, then x402-paid ReadFetch tools; for hosts that cannot sign x402.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
EVM_PRIVATE_KEY, READFETCH_MAX_PAYMENT_USD, READFETCH_MCP_URL, READFETCH_DEVValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
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": {
"x402-proxy": {
"command": "npx",
"args": [
"-y",
"@readfetch/mcp-x402-proxy"
],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"READFETCH_MAX_PAYMENT_USD": "your-value",
"READFETCH_MCP_URL": "your-value",
"READFETCH_DEV": "your-value"
}
}
}
}Run this in your terminal
claude mcp add x402-proxy --env EVM_PRIVATE_KEY=your-value --env READFETCH_MAX_PAYMENT_USD=your-value --env READFETCH_MCP_URL=your-value --env READFETCH_DEV=your-value -- npx -y @readfetch/mcp-x402-proxyFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"x402-proxy": {
"command": "npx",
"args": [
"-y",
"@readfetch/mcp-x402-proxy"
],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"READFETCH_MAX_PAYMENT_USD": "your-value",
"READFETCH_MCP_URL": "your-value",
"READFETCH_DEV": "your-value"
}
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"x402-proxy": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@readfetch/mcp-x402-proxy"
],
"env": {
"EVM_PRIVATE_KEY": "your-value",
"READFETCH_MAX_PAYMENT_USD": "your-value",
"READFETCH_MCP_URL": "your-value",
"READFETCH_DEV": "your-value"
}
}
}
}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.
READFETCH_MAX_PAYMENT_USD envREADFETCH_MCP_URL envREADFETCH_DEV envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account readfetch, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: EVM_PRIVATE_KEY
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).
The GitHub repo last changed –, and the latest version (0.1.17) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, FactLot
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
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.
Most MCP hosts (Cursor, Claude Desktop, etc.) cannot attach PAYMENT-SIGNATURE on tools/call. This stdio MCP server lists tools from https://readfetch.com/mcp, executes `tools/call` against `/v1/{endpoint}` on the same host (so HTTP 402 triggers @x402/fetch payment), and signs retries automatically.
readfetch_text, …). `tools/list` does not load your key; the first `tools/call` does.{
"mcpServers": { "readfetch": { "command": "npx", "args": ["-y", "@readfetch/mcp-x402-proxy@0.1.14"], "env": { "EVM_PRIVATE_KEY": "0xYOUR_KEY" } } } }
From a checkout:
{
"mcpServers": { "readfetch": { "command": "node", "args": ["/absolute/path/to/readfetch/tools/mcp-x402-proxy/index.mjs"], "env": { "EVM_PRIVATE_KEY": "0xYOUR_KEY" } } } }
Optional: READFETCH_MCP_URL (default https://readfetch.com/mcp; https only for readfetch.com / www.readfetch.com, or localhost / 127.0.0.1 / [::1] with READFETCH_DEV=1). Upstream redirects are rejected. READFETCH_MAX_PAYMENT_USD (default 1, max 100) caps each x402 authorization. On readfetch.com upstream, payments must match `READFETCH_EXPECTED_PAYTO` (default catalog payee). `READFETCH_DEV=1` is only for local MCP URLs and enables Sepolia there — never set it when READFETCH_MCP_URL points at production.
Wallet risk: any tool the model invokes (readfetch_crawl, batch, …) can spend USDC from your key until the wallet is empty (subject to the per-payment cap). Use a dedicated low-balance wallet.
Install from a checkout:
cd tools/mcp-x402-proxy
npm ci
npm ci in a git checkout uses the committed `package-lock.json`. `npx @readfetch/mcp-x402-proxy` installs exact dependency versions pinned in package.json (npm does not ship the lockfile in the published tarball).
npm ci && npm test
npm run smoke # readfetch_probe (free) SMOKE_TOOL=readfetch_text npm run smoke # paid REST path; needs Base USDC
From this directory — not the repo root:
cd tools/mcp-x402-proxy
npm login # user must own or belong to npm org @readfetch npm publish --access public # first publish of a scoped package
Wrong: npm publish @readfetch/mcp-x402-proxy from ReadFetch/ (404 — nothing to publish there).
If the @readfetch org does not exist on npmjs.com, create it or temporarily change name in package.json to an unscoped name you control.
readfetch_probe with { "url": "…" } (free; may include preview ~400 chars when HTML, not a bot wall)readfetch_text with the same urlchallenge: true, use readfetch_scrape (then readfetch_scrape_residential if needed)After a confusing 402, MCP result, or doc mismatch, call `readfetch_feedback` (free — no EVM_PRIVATE_KEY) with:
{ "request_id": "<X-Request-Id from that call>", "category": "integration", "message": "…" }
Paid delivery disputes use `POST /v1/claims`, not feedback. Details: readfetch.com/docs#feedback.
awal x402 pay https://readfetch.com/v1/text -d '{"url":"…"}' or @x402/fetch in your app/mcpSee also readfetch integrations and SKILL.md.
Directory: Official MCP Registry io.github.readfetch/mcp-x402-proxy · Glama listing steps in readfetch/readfetch docs/GLAMA.md (operator).