26,823
servers probed
On October 12, 2026 we completed a full runtime survey of the public MCP registry: every reachable server was handshaked, every open tool surface enumerated, every parameter schema kept as evidence. This report is the graded summary of that census.
Registry metadata says where a server lives. It never says what the server does.
Every published MCP package and registry entry lists package names and remote endpoints. None of them — at any layer — carries tool definitions. Published npm packages don't retain a static manifest either. The only source of truth for a server's tool surface is a live MCP handshake followed by tools/list.
So we connected to all 26,823 candidate endpoints, one at a time, and kept what came back. The two data files behind every number on this page carry SHA-256 manifests you can check yourself, before you pay us anything.
Analysis is our work product; the snapshot is openly licensed. You can reproduce everything before the invoice clears.
Every open server graded A/B/C against five parameter-risk classes; the top 100 by exposure listed with evidence line references back into the frozen dataset.
SSRF · command injection · credential exfiltration · tool poisoning · dependency rug-pull — each high-consequence tool mapped to a class, each count recomputable from the raw lines.
Hand us your server list and we grade each one on the same frozen baseline: exposure percentile, named findings, and where you sit versus the ecosystem.
A methodology appendix states classification rules and thresholds plainly. If you disagree with a grade, you can show exactly where and why — that's the point.
Three ways to buy. Delivery is calendar-days, not quarters.
We reply within 24 hours with the sample report and an invoice link. Purchase orders and net-30 accepted.
By submitting you agree to be contacted about this order. No telemetry, no user-data resale. "MCP" refers to the Model Context Protocol ecosystem; census scope is the public registry snapshot of 2026-10-12. IETF drafts referenced on other pages of this site are individual submissions, not RFCs or IETF endorsement.