Read-only static diagnostics for local stdio MCP configuration
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-config-doctor","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 Config Doctor 0.1 MCP Config Doctor is a local, read-only static scanner for one named MCP server. It checks known configuration surfaces for Claude Desktop, Claude Code, Codex, and VS Code, then prints deterministic findings and manual next steps. Version 0.1.0 is a deliberately narrow public beta. It performs static checks only, makes no runtime-success promise, and does not include checkout or license enforcement. USD 19 remains a pricing hypothesis rather than a current charge. ## Install and run locally Python 3.11 or newer is the supported runtime. The package has no runtime dependencies and does not require network access. ```bash python3 -m venv .venv .venv/bin/pip install . mcp-doctor scan --server filesystem ``` Narrow the scan or emit machine-readable output: ```bash mcp-doctor scan --server filesystem --client codex --format json ``` The command prints the paths it checked, but replaces the home and project roots with `~` and `<project>`. It never prints environment values or argument values. ## What v0 checks - known user and project/workspace configuration locations; - duplicate, shadowed, absent, and ambiguous-scope definitions; - local stdio command resolution in the current process environment; - configured `cwd`, path-like arguments, and named environment references; - wrapper/no-TTY and container/localhost risk patterns; - malformed, duplicate-key, unreadable, oversized, and unsupported configs; - text and JSON reports using the same versioned finding catalog. The full path matrix is in [docs/config-matrix.md](docs/config-matrix.md), and the stable code contract is in [docs/findings.md](docs/findings.md). ## Exit codes - `0`: reliable static scan with no actionable `FAIL`; warnings may remain. - `1`: reliable scan found at least one actionable `FAIL`. - `2`: invalid input, parsing, permission, unsupported transport/shape, or ambiguous precedence prevented a reliable conclusion. ## Safety and privacy boundary The installed `…
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.