Zero LLM, zero network, zero API keys - a CI-gate harness for stdio MCPs.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-stdio-test","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mcp-stdio-test [](https://pypi.org/project/mcp-stdio-test/) [](https://pypi.org/project/mcp-stdio-test/) [](https://github.com/dtchen07/mcp-stdio-test/actions/workflows/ci.yml) [](LICENSE) [](https://pypi.org/project/mcp-stdio-test/) **Zero LLM, zero network, zero API keys - a CI-gate harness for stdio MCPs.** `mcp-stdio-test` spawns an MCP server over stdio, runs the JSON-RPC initialize handshake, and lets you assert on `tools/list` or call any tool - all with CI-friendly exit codes. It is the thing you wire into `.github/workflows/ci.yml` so a missing tool or a broken signature turns the pipeline red without anyone reading the output. If you want a scored quality report, use `mcp-doctor`. If you want rule-based lint, use `mcp-lint`. If you want agent-driven end-to-end evaluation with cost tracking, use `mcp-tester`. If you want to click through your server, use MCP Inspector. `mcp-stdio-test` is the harness. ## Install ```bash pip install mcp-stdio-test # or pipx install mcp-stdio-test # or (no install) uvx mcp-stdio-test --help ``` Zero runtime dependencies. Python 3.10+. ## 60-second quickstart ```bash # 1. Confirm the tool works on your machine. mcp-stdio-test doctor # 2. Point it at any stdio MCP server script. mcp-stdio-test path/to/server.py --list-tools # 3. Gate CI on the tool inventory. mcp-stdio-test path/to/server.py --list-tools --expect-count 5 --expect-tool search ``` A non-zero exit code means something regressed. No log-scraping required. ## CLI reference | Flag | Purpose | |---|---| | `<server>` | Path to the MCP server script to spawn. | | `--pyexe PATH` | Python interpreter to run…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.