Check an MCP server before you install
Health and ownership for 27,000+ servers. Every claim links to public evidence. Look one up, audit your whole config, or let your agent check before every call. Free to try.
free · 10/day · no signup·Lookup·Preflight·Audit a config·API for agents
Current daily projection · source 2026-09-13 17:41:05 · generated 2026-09-13T17:41:08.381Z
- loading…
Directories list. We check.
Is it the vendor’s server or a lookalike? Still maintained? What can you open as proof?
Your agent checks. Every time.
One call audits a whole MCP config. One rule line makes the agent run it before every install or tool call. One cursor tells it what changed since last time. Nothing to remember, nothing to re-read.
# the whole recurrence mechanism — paste into your agent's instructions
Before adding, enabling or calling any MCP server, run a Census stamp. Stop on BLOCK. Ask on REVIEW.Audit your config → · Claude Code, Codex, Cursor, VS Code → · GitHub Action →
What changed since you last looked
Every cron writes what it saw: a server appears in the registry, a hosted endpoint goes down or comes back, a tool list changes, health or verification flips, an endpoint moves. Pull it with a cursor. No key, no credits.
- loading…
16% have a verified problem
Gone repo, archived, deprecated package, or no push in 6+ months. Unknown stays unknown.
View as table
| Verdict | Servers |
|---|---|
| Healthy (repo active <6mo) | 10,444 |
| Unknown (insufficient evidence) | 2,496 |
| Has verified issues | 2,442 |
Problems by type · categories
View as table
| Problem | Servers |
|---|---|
| GitHub repo gone (deleted/private) | 1,880 |
| No repo push in 6+ months | 299 |
| npm package deprecated | 218 |
| registry_deprecated | 166 |
| GitHub repo archived | 126 |
| npm package missing | 25 |
| PyPI package missing | 15 |
View as table
| Category | Servers |
|---|---|
| dev-tools | 11,697 |
| ai-ml | 1,943 |
| api-integration | 1,672 |
| security | 864 |
| finance | 847 |
| communication | 544 |
| media | 536 |
| files-documents | 461 |
| data-analytics | 406 |
| databases | 399 |
| weather-geo | 377 |
| productivity | 302 |
Free to check. Credits when agents run at scale.
Team $49/mo · 10,000 credits. Search/lookup 1 · config audit 1 per config per day · preflight/stamp 5 · watch 10. Repeats same UTC day are free. The change feed is unmetered. A daily audit of a 10-server config stays inside the free grant.
Should I install this MCP server?
Look it up first. You get healthy / issues / unknown from repo, package, and registry facts. Not a pen-test. Try free →
Can my agent check automatically?
Yes. Add the rule line above to its instructions. It runs census_stamp for one server or census_audit_config for the whole config before it connects. Stop on BLOCK. Ask on REVIEW. PASS is not a sandbox. Setup →
What does UNKNOWN mean?
The Census has no row for that entry yet: a local script, a Docker image, or a package nobody has submitted. It is not a pass. Packages seen in audits are queued for verification and land in the Census once the evidence holds. Audit contract →
What this is not
The MCP Census is a live registry health and identity check. It is not a full security audit, pen-test, compliance certification, or guarantee that a server is safe to run in production. Unknown means we lack evidence, not that the server is fine. Methodology →
[email protected] · 14-day refunds · ACL applies · no marketing cookies
Support is human. Data is public sources; the product is the live check.
pricing · agent-setup/prompt.md · llms.txt · manual install →