Show HN: Paste your MCP config, see what each server does at startup

Each of those 7 servers is recorded with the name it asked for and the line of its README that does not contain it. Nothing left the machine: the room has no route off the host, so every name answered to the loopback address and no connection completed.

24 servers offered a tool their README does not name — 1,143 tools were offered in total and none was called. Read that second figure with the caveat attached: this rule reads only the README that shipped in the package, so a server documenting its tools in a reference file beside it shows every tool as unnamed, and 10 of those servers have a README under three kilobytes. A large count here is a fact about the rule as much as about the package.

2 did both. The remaining 38 had nothing found, which is not the same as a clean sweep — see below.

67 npm packages, each measured from its name alone: installed, started in a room with no route to the internet and no real credentials, asked for its list of tools, and compared against its own README. No tool was called. Measured 2026-10-31.

Not calibration-backed. The calibration behind the ten curated measurements proves the instrument catches planted claims about what a tool did. Level 1 calls no tool and reads each README by a stated rule rather than by a person, so nothing in that calibration speaks to these pages.

A website counts as declared only if the README names it. A tool counts as documented only if the README names it as a whole word.

This is not a ranking of the most-used servers. The set measured is whatever two registry searches returned, read by hand for whether each package is a server that starts without a credential. Download figures decided nothing about the order of this table, which is alphabetical by package, and four widely used servers are measured here that neither search returned at all. Nothing on this page says one server is more used, better or worse than another.

All 67 packages started, so no row says could not start. Evidence for every row — the full trace, the tool list, the README digest and each citation — is in level1/evidence/, one JSON file per package, beside the code that produced it.

29 pages are not published yet. Each reports a finding, and a page reporting a finding goes up only after its maintainers have been notified and three days have passed. The counts above include them; the pages and the package names do not appear until then. How that works