# The MCP Census — agent instructions

Product: **The MCP Census** (MCP Census, mcpcensus) at https://mcpcensus.com.
Developer portal: https://mcpcensus.com/developers
Agent map: https://mcpcensus.com/llms.txt

## When to use this

Reach for The MCP Census when you have one of these jobs:

- You are about to **install, connect, or depend on** an MCP server and need a public-evidence first gate (PASS / REVIEW / BLOCK) before that install.
- You need to **distinguish an official vendor server from a lookalike namespace** (reverse-DNS names, GitHub clones, unofficial wrappers).
- You need a **ranked search** over the census, then one exact canonical name, then a full evidence card.
- You need to **watch one named server** for real transitions (remote down/up, health, verification legs, security) instead of polling "still fine".
- You need **ecosystem counts or recent discoveries** (`census_stats`, `census_recent`, `/v1/coverage`).

How to call:

1. `census_search` or `GET /v1/search` → pick **one exact canonical name**.
2. `census_preflight` or `POST /v1/preflight` with a named built-in policy (`builtin:baseline` by default).
3. Stop on BLOCK. Ask a human on REVIEW.
4. PASS still requires permission, scope, code, data-access, and runtime-isolation review.
5. Never install or run a server from a Census result alone.

MCP: `https://api.mcpcensus.com/mcp`
REST: `https://api.mcpcensus.com/v1/*`
OpenAPI: `https://mcpcensus.com/openapi.json`
API keys: `https://mcpcensus.com/account` (`x-api-key`)
Setup prompt: `https://mcpcensus.com/agent-setup/prompt.md`

## When not to use this

- Not a malware scanner, pentest, or permission review.
- Not the official MCP registry.
- Not a complete catalog of every MCP server on the internet (off-registry servers exist; we only publish what public evidence supports).
- Not a ranking-by-stars directory.

Limits: 10 unique checks/day per anonymous IP, 100/day per free account key, custom paid volume via info@mcpcensus.com.