Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read-only preflight for any MCP or x402 endpoint: handshake, tool schemas, 402 drift.
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.
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": {
"mcpreflight": {
"command": "npx",
"args": [
"-y",
"@eidonze/mcpreflight",
"mcpreflight-mcp"
]
}
}
}Run this in your terminal
claude mcp add mcpreflight -- npx -y @eidonze/mcpreflight mcpreflight-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mcpreflight": {
"command": "npx",
"args": [
"-y",
"@eidonze/mcpreflight",
"mcpreflight-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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mcpreflight": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@eidonze/mcpreflight",
"mcpreflight-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.
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 xka0085-byte, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.6.0) reached the registry 4 days ago.
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, MCP Server Autocad Lisp Helper
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.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
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.
Point it at any MCP or x402 endpoint and get a verdict in one command. Read-only: no API key, no wallet, no tool calls.
npx -y @eidonze/mcpreflight schema https://your-mcp-server.example/mcp
Status: PASS | FAIL | UNKNOWN exit 0 | 1 | 2, so CI can gate on it
Reach for it when an agent client, a buyer, or a CI job is about to depend on an endpoint whose source you cannot read, including endpoints you do not own. It reads only what the endpoint already sends to any anonymous caller: the initialize handshake, tools/list, and the HTTP 402 / x402 payment document.
| Form | Run it | Use it for |
|---|---|---|
| CLI | npx -y @eidonze/mcpreflight ... | one-off checks and scripts |
| Homebrew | brew install xka0085-byte/mcpreflight/mcpreflight | a machine-wide mcpreflight on PATH, macOS or Linux |
| GitHub Action | uses: xka0085-byte/mcpreflight@v1 | fail a PR when a handshake, a tool schema or an x402 challenge drifts |
| stdio MCP server | npx -y -p @eidonze/mcpreflight mcpreflight-mcp | let an agent check an endpoint before it connects |
No install to try it: run the check in the browser, free and without signup: check-your-mcp-endpoint
Listed in the official MCP Registry as io.github.xka0085-byte/mcpreflight (browse) and on the GitHub Marketplace.
Read-only MCP and x402 preflight: it reads initialize + tools/list and x402 payment documents. No API key, no wallet, no payment, no tool calls.
This is an endpoint preflight, not a source audit. Tools that read your repository or fuzz a server you launch need a checkout and a start command; this one needs only a URL, so it can check the deployment an agent is about to connect to, including one you do not own.
Search "MCP preflight" and you also meet kenimo49/mcp-preflight, now published as mcp-scorecard. Both check an MCP server before something depends on it; the input and the findings differ.
This repo (mcpreflight) | mcp-scorecard (kenimo49) | |
|---|---|---|
| Input | a deployment URL, including one you do not own | a local checkout, a localhost URL, or a pypi: package |
| Reads | initialize, tools/list, and the HTTP 402 / x402 payment document, anonymously | per-turn token footprint, use-case scoping of each tool, security rules, name safety |
| Answers | will this deployed endpoint answer an agent, and does its payment challenge still hold? | is this server cheap and clear enough for an LLM to use, before you publish it? |
One grades the source you have; the other checks the endpoint you are about to depend on.
The same read-only check runs weekly against every remote endpoint listed in the official MCP Registry, and the results are published as pages and as JSON:
/trust/api/{slug}.json per endpoint, plus batch indexes and a JSON Schema. No key, no signup, no rate limit.Read the vocabulary before quoting any number: in the 2026-11-02 scan, 20,701 endpoints answered anonymously (PASS), 10,236 refused with 401 because they require credentials by design (AUTH_GATED), 167 were reachable but invalid (FAIL), and 4,223 gave no anonymous handshake (UNKNOWN, usually an auth wall we cannot see past). A "dead MCP servers" count taken from this data would be wrong — 41% of the registry cannot be checked without credentials at all.
The stdio entry point is bin/mcpreflight-mcp.mjs, published as the mcpreflight-mcp bin in the same npm package. It implements the MCP lifecycle a client expects: initialize returns serverInfo mcpreflight with the package version, notifications/initialized is accepted, and tools/list returns two tools.
| Tool | What it does |
|---|---|
schema_check | Runs the read-only preflight against a server URL: initialize handshake, tools/list, then tool input schema validation. Returns PASS/FAIL/UNKNOWN with findings. Never calls a tool, never reads data. |
x402_inspect | Reads an HTTP 402 challenge without paying: validates the payment document shape, the accepts[] entries and discovery manifests. Never signs or settles. |
Add it to an MCP client:
{
"mcpServers": { "mcpreflight": { "command": "npx", "args": ["-y", "-p", "@eidonze/mcpreflight", "mcpreflight-mcp"] } } }
Both tools do the same work as the CLI and return the same findings, so an agent can check an endpoint before it connects to it. Read-only by construction: the transport issues only GET and POST to the URL you pass, holds no key and has no wallet.
npx @eidonze/mcpreflight@0.2.0 schema https://joxo.ai/api/mcp and got UNKNOWN: MCP initialize returned HTTP 401 against a deliberate OAuth 2.1 gate (#50). That report is the reason 0.3.0 classifies an OAuth challenge as AUTH_GATED, with the RFC 9728 resource metadata verified, instead of reading as a dead endpoint. They re-checked on 2026-11-01 and closed it: "The endpoint is sign-in only, so no anonymous handshake is expected. Thanks for the AUTH_GATED handling; closing." (#50).@eidonze/mcpdoctor@0.1.8 (the earlier npm name) now exits 0 on their endpoint, with the anonymous tools/list payload down from 1,399,189 to 550,377 bytes — under the scanner's 1 MiB limit (#11).These are examples of the check being run, not endorsements or a claim that a PASS makes a server safe.
Exit codes are stable for CI: 0 PASS, 1 FAIL, 2 UNKNOWN/network, 3 usage. Requires Node.js 18+.
mode is schema (MCP handshake plus tool schemas), inspect (one-off x402 preflight), baseline (record the current 402 challenge shape) or drift (fail the job when that shape moves away from the committed baseline). The report is also appended to the job summary, and steps. .outputs.status carries the exit code so later steps can branch on it without parsing logs.
Check an MCP server without calling any tools:
npx @eidonze/mcpreflight schema https://your-mcp-server.example/mcp --json
Check an x402 endpoint without paying:
npx @eidonze/mcpreflight inspect https://your-api.example/paid --method=POST --json
npx @eidonze/mcpreflight inspect https://your-api.example/paid --x402 # payment layer only, one request
Requires Node.js 18+. No API key or wallet is needed.
Example schema run against a live endpoint:
$ npx @eidonze/mcpreflight schema https://your-mcp-server.example/mcp
MCP Tool Schema Report
The exact same run against a healthy server prints Status: PASS and exits 0, so CI can gate on it.
| Command | Checks | Does not do |
|---|---|---|
schema | MCP initialize, tools/list, tool names, descriptions, and JSON schemas | Does not call tools or prove runtime behavior |
inspect | HTTP 402, x402 v1/v2 payment document, accepts[], discovery manifests, latency and response digest | Does not sign, pay, settle, retry, or verify delivery |
inspect --x402 | The payment layer only: one request, the 402 challenge and its accepts[] entries, no MCP handshake or discovery probes | Same limits, and it says nothing about the MCP endpoint behind the payment |
Exit codes are stable for automation: 0 PASS, 1 FAIL, 2 UNKNOWN/network error, 3 usage error.
mcpreflight is a protocol- and schema-level preflight, not a security audit. It does not:
A PASS means the observed handshake and schemas were well-formed at scan time. Nothing more.
Add a read-only check to pull requests:
name: MCP Trust Check
on: [pull_request]
jobs: mcp-trust: runs-on: ubuntu-latest steps:
Use mode: x402 when you only care about the payment layer: one request, the 402 challenge and its accepts[], no handshake, no discovery probes. Use mode: inspect for the full report. The action fails on FAIL or UNKNOWN by default; set fail-on: false for an informational check. Looking for it in the Marketplace? Search "MCP Trust Preflight" or "mcp server test", or browse the mcp-trust-preflight listing.
Start a new MCP project with this check already wired in:
The check is read-only and should target a public test endpoint. Do not place private keys or credentials in workflow inputs.
PASS means the observed response matched the checks in this version. It is not a security audit, protocol certification, payment-success guarantee, or proof that an endpoint is s
Only the beginning is shown; read the rest in the repo