MCP Census
MCP Census is a public-evidence gate that validates Model Context Protocol servers before installation by checking registry, GitHub, npm, and PyPI sources. It returns PASS, REVIEW, BLOCK, or UNKNOWN verdicts and operates as a first-line vetting tool, not a malware scanner. Agencies can audit entire MCP configs via API, run preflight checks in GitHub Actions CI pipelines, track registry changes via change feeds, and subscribe webhooks to monitor specific servers. The service integrates natively with Claude Code, Codex, Cursor, VS Code, and GitHub Actions, making it accessible to development teams already using these tools. Best suited for agencies building AI agents or infrastructure that depend on third-party MCP servers and need to gate untrusted installations.
MCP Census is a public-evidence gate, priced at $19 a month on the builder plan, integrating with Claude Code, Codex, Cursor and VS Code. InnovaAI rates it 5.6 of 10 for agency resale.
Agency Audit
MCP Census validates Model Context Protocol servers against public evidence (GitHub, npm, PyPI, registry) before installation, returning PASS, REVIEW, BLOCK, or UNKNOWN verdicts. Agencies building AI agents that deploy MCP servers can integrate Census checks into Claude Code, Codex, Cursor, or VS Code workflows, or run preflight audits in CI via GitHub Actions. The service is most valuable for development teams that need to gate untrusted server installations and security-conscious shops building agent infrastructure for clients. However, it solves a narrow problem: MCP server vetting, not general AI agent security or compliance.
5.6/10
52%
2d 1 to 2 days
- You build custom AI agents for clients using MCP servers and need to gate server installations before deployment.
- Your development team runs MCP configs in CI and requires preflight checks to fail pull requests on BLOCK verdicts.
- You serve security-conscious engineering teams or agent platform operators who audit third-party MCP dependencies.
- Your clients do not use Model Context Protocol or MCP-based agents in their workflows.
- You need a general-purpose malware scanner or security compliance tool; MCP Census is MCP-specific only.
- You require white-label branding for client-facing dashboards; MCP Census does not offer a verified white-label program.
Profit Path
$19/mo
$1K–$3K/project
Hybrid
Planning benchmark at United States price levels. Not a measured market survey.
Platform Features
Core capabilities of MCP Census
Server lookup with public evidence
Query any MCP server by name and receive PASS, REVIEW, BLOCK, or UNKNOWN verdicts based on registry, GitHub, npm, and PyPI evidence. Free tier allows 10 unique lookups per day per IP without signup.
Config audit API
Submit an entire MCP config (.mcp.json) in one API call to audit all servers at once. Useful for agencies validating client agent configurations before deployment.
CI preflight checks
Integrate with GitHub Actions to fail pull requests when MCP servers return BLOCK verdicts. Prevents unsafe server installations from reaching production.
Change feed tracking
Subscribe to registry changes since a cursor to monitor when new MCP servers are added or existing servers are updated. Enables agencies to track ecosystem shifts affecting client deployments.
Webhook watches
Set up webhooks to monitor a specific MCP server for changes. Alerts agencies when a server they depend on is modified or flagged.
MCP and REST APIs
Access Census data via native MCP endpoint or REST API. Allows agents to call Census directly or integrate into custom workflows without SDK dependencies.
What Makes MCP Census Different
Unique advantages vs similar tools in this niche
Returns a policy verdict (PASS/REVIEW/BLOCK/UNKNOWN) instead of a directory listing
vs Smithery, Glama, and mcp.so which help find or host serversThe Census checks public evidence and returns a policy decision, and does not host servers or sign users into tools.
Audits an entire MCP config in one call with per-entry verdicts
vs Manual per-server lookups across registriesPOST the config to /v1/audit and get one PASS, REVIEW, BLOCK, or UNKNOWN line per entry.
Cursor-based change feed of registry and health changes
vs Re-reading directories manually to spot changesGET /v1/changes?since=cursor returns verified_change, tools_changed, health_change, and remote_up events.
Latest Updates
Recent releases and improvements for MCP Census
Trust scoring v3.2
Improvement2026-07-27Corroboration cap preventing self-declared identities from earning score without independent evidence, brand impersonation detection, pillar-based scoring with traceable evidence URLs, and live endpoint verification including OAuth-protected servers.
Discovery beyond the registry
New2026-07-27Independent discovery and verification of vendors shipping MCP servers without registering, conventional endpoint discovery, machine-readable manifest and llms.txt support, and evidence-gated publication.
Search precision
Improvement2026-07-27Domain queries resolving on exact ownership boundaries, match tiers separating real name matches from passing mentions, and audited confirmed_absent verdicts with review trails.
Platform updates
New2026-07-27Lookup table with frozen identity columns, public Coverage transparency page and /v1/coverage endpoint, per-server watches with webhook and email delivery, REST and MCP APIs with one-click install, multi-provider SSO, and Learn reference material.
Investment ROI Calculator
Value equation analysis for MCP Census, based on the Hormozi framework
What is the Hormozi framework? A four-factor score: (what the service delivers × how reliably it delivers) divided by (how long it takes × how much effort it requires). A higher Value Multiplier means a better return on the time and money invested: faster, easier, and more proven results.
2.1× value multiple: invest $19/mo and agencies typically charge $1K–$3K/project for the work it powers.
Why This Succeeds
Higher is betterClient Results Potential
What your clients actually get
Incremental gains: position as part of a larger solution stack
The MCP Census checks public evidence for an MCP server and returns PASS, REVIEW, BLOCK, or UNKNOWN.
Reliability Score
How consistently this delivers results
Early-stage track record: validate with a small pilot first
7,320 servers 2,323 GitHub 822 issues 4,624 remotes
Implementation Challenges
Lower is betterTime to First Revenue
How long until you can start earning
Standard ramp-up: accelerate to 1 day with Academy SOPs
Expect a few days from signup to first client delivery
Setup Effort
What it takes to get running
Near-turnkey: minimal setup before you can sell
Moderate effort: standard configuration with some customization needed
Viable opportunity. MCP Census returns 2.1× on investment. Focus on the highest-margin service packages to maximize return.
Pricing
MCP Census platform cost to your agency
Starts at $19/mo (builder), scales to $49/mo (Team)
free
- Account + API key. No card.
- Monthly grant. No grant rollover.
- Anonymous, no account: 10 unique lookups/day per IP
- 1,000 credits each UTC month
builder
- 2,000 credits each UTC month
- Purchased credits never expire
- REST, MCP, stamp, watches
Team
- 10,000 credits each UTC month
Add-ons
Optional extras priced on top of any main plan
No verified white-label program for MCP Census: client-facing delivery runs under the platform's native branding.
Market Intelligence
How agencies monetize MCP Census: real offer economics and market positioning
- Agencies building AI agents that install MCP servers
- Development teams running MCP configs in CI
- Security-conscious engineering teams
- Agencies needing full penetration testing or malware scanning
- Teams without any MCP/agent tooling
Project-Based
ai-toolsAgency charges per-project fee for implementation. Ongoing optimization as optional retainer.
Offer Economics: What You Charge vs. What It Costs
Margin includes platform cost + agency labor at $75/hr.
Local small businesses or solo practitioners deploying their first MCP-connected AI tool and needing a one-time security gate check before go-live
Funded startups or regional brands with 10-50 employees actively integrating multiple MCP servers into their AI stack and needing a structured compliance baseline
Mid-market companies with 50-500 employees running multi-team AI deployments across several MCP-connected services requiring ongoing governance and audit trails
Enterprise organizations with 500+ employees and complex AI supply chains requiring a fully operationalized MCP server vetting program with executive reporting and continuous monitoring
Scale Economics: Based on Starter Offer
Using MCP Census SMB Audit at $1.8K/client. Platform: $19/mo. Labor: 4h/client × $75/hr.
Net = MRR - platform cost - labor (4h/client × $75/hr).
Investment Decision Framework
Strategic vetting analysis for MCP Census
Consider
Favorable fit, worth a closer look
Buy If
5You build custom AI agents for clients using MCP servers and need to gate server installations before deployment.
Your development team runs MCP configs in CI and requires preflight checks to fail pull requests on BLOCK verdicts.
You serve security-conscious engineering teams or agent platform operators who audit third-party MCP dependencies.
You need to track registry changes and subscribe webhooks to monitor specific MCP servers for your clients.
You operate a multi-tenant agent platform and audit entire MCP configs (.mcp.json) in a single API call per client.
Skip If
5Your clients do not use Model Context Protocol or MCP-based agents in their workflows.
You need a general-purpose malware scanner or security compliance tool; MCP Census is MCP-specific only.
You require white-label branding for client-facing dashboards; MCP Census does not offer a verified white-label program.
Your clients demand HIPAA, FedRAMP, or other regulated compliance certifications beyond SOC2.
You need a managed security service with 24/7 support; MCP Census is a self-service API with community support.
Bottom Line
MCP Census validates Model Context Protocol servers against public evidence (GitHub, npm, PyPI, registry) before installation, returning PASS, REVIEW, BLOCK, or UNKNOWN verdicts. Agencies building AI agents that deploy MCP servers can integrate Census checks into Claude Code, Codex, Cursor, or VS Code workflows, or run preflight audits in CI via GitHub Actions. The service is most valuable for development teams that need to gate untrusted server installations and security-conscious shops building agent infrastructure for clients. However, it solves a narrow problem: MCP server vetting, not general AI agent security or compliance.
Reality Check
MCP Census is explicitly not a malware scanner or pen-test tool, so agencies cannot position it as a comprehensive security solution. Adoption depends on client adoption of MCP-based agents, which remains a niche workflow outside mainstream AI tooling. Resale potential is limited to agencies already selling agent development or infrastructure services.
Moderate effort: standard configuration with some customization needed
Academy for MCP Census
Work through it in order: the course for this service first, then the modules behind it.
No Academy modules are published for this service yet. Browse the full Academy
Why this category matters
The commercial case before the tooling.
Core concepts
The mental model you need to price and scope the work.
- Concentration Risk LedgerConcept
Concentration Risk Ledger is a framework for tracking how much of an agency's delivery capacity depends on any single model provider, region, or price tier. The unit of analysis is not the vendor relationship but the retainer: for each client engagement, list which workflows break if one provider raises prices, degrades quality, or restricts access. Forrester warned in October 2026 that AI supply chains hide single points of failure in plain sight, and the same week Anthropic cut Claude Haiku 5.5 to $0.10 per million input tokens while OpenAI shipped GPT-6 to 1.2 billion weekly users, both reminders that pricing and capability floors move fast. An agency running every client summarization job through one API has an unpriced liability. The ledger converts that into a number: percentage of monthly delivery hours exposed, and the cost of a routing layer that reduces it.
- Provider Concentration RatioConcept
Provider Concentration Ratio is the share of an agency's live client delivery that depends on a single model vendor, measured in billable projects rather than API keys. A retainer running three client builds on one provider's API looks diversified on an invoice and is not: a pricing change, a deprecation, or a guardrail shift hits all three at once. The ratio matters because infrastructure cost is a pass-through that agencies rarely reprice mid-contract, so a vendor move lands directly on margin. The practical test is to count distinct providers behind each deliverable and flag any client where one vendor carries more than half the inference load. Routing layers such as OpenRouter, Portkey, and Helicone exist to make that count adjustable without rewriting application code. The same discipline applies to compute: industry executives expect only 7 to 10 of hundreds of AI cloud providers to survive consolidation, so GPU capacity booked with a single neocloud carries the same concentration risk as a single-model stack.
- Inference Cost FloorConcept
Inference Cost Floor is the practice of tracking the lowest available price per million tokens for a capability tier, then treating every drop as a trigger to re-price client retainers rather than a windfall to bank. Agencies that price AI work on today's model economics get undercut the moment a cheaper tier ships, because the client's procurement team reads the same launch posts. Anthropic's Claude Haiku 5.5 arrived at $0.10 per million input tokens with a 1 million token context window, which resets what high-volume document summarization and campaign analysis should cost a client. The framework has three moves: benchmark your current blended cost per deliverable, set a review cadence tied to model releases, and pre-agree with clients that savings split rather than vanish. Agencies running fixed-fee AI retainers without a floor review are quietly donating margin every quarter.
Decision and risk
How to judge the fit, and the ways it goes wrong.
- AI Infrastructure Rule: Price the Exit Before You Price the InferenceEvaluation Rule
Treat provider portability as a delivery requirement: put a gateway or routing layer in front of every model call, and price the migration path into the retainer before the first token is billed.
- AI Infrastructure Rule: Route Through a Gateway Before You Sign a Second Model ContractEvaluation Rule
Stand up a gateway layer that logs, caches, and routes requests across at least two providers before any single-model contract becomes load-bearing for a client retainer.
- The Single-Provider Trap: Why AI Infrastructure Stalls When One Model Vendor Owns the StackFailure Pattern
- The Token Bill Trap: Why AI Infrastructure Costs Outrun Agency RetainersFailure Pattern
8 modules selected for MCP Census
Frequently Asked Questions
Answers about pricing, setup, implementation
MCP Census lists 3 plans; the paid ones run from $19 a month (builder) to $49 a month (Team). The typical margin on reselling MCP Census is 52% of the fee, after the platform and labor at $75 an hour.
Free plan with 1,000 credits each UTC month and no card required. Builder $19/month with 2,000 credits and purchased credits that never expire. Team $49/month with 10,000 credits. Add-on credit pack of 1,000 credits for $9 one-time. Free tier also allows 10 unique lookups per day per IP without an account.
No verified white-label program. Client-facing surfaces display the MCP Census brand, so you cannot present a fully branded portal to end clients. The service is best positioned as a backend audit tool for your own infrastructure rather than a client-facing product.
Yes. MCP Census works natively with Claude Code, Codex, Cursor, VS Code, and GitHub Actions. You can embed Census checks directly into these IDEs or call the MCP endpoint at https://api.mcpcensus.com/mcp without authentication for basic queries.
Setup depends on your integration method. Free lookups require no account and work immediately. Paid accounts activate instantly after signup. CI integration via GitHub Actions typically takes 15-30 minutes to configure per client repository. Webhook setup takes 5-10 minutes per server you want to monitor.
Development teams building AI agents that install MCP servers, security-conscious engineering teams that audit third-party dependencies, agent platform operators managing multi-tenant MCP deployments, and SaaS startups integrating MCP-based AI tooling into their products.
MCP Census offers a 14-day refund on unused paid access. After cancellation, your account reverts to the free tier with 1,000 credits per UTC month. Purchased credits that never expire remain available on the free plan.
Yes. The config audit API accepts an entire .mcp.json file and returns verdicts for all servers in one call. The Team plan ($49/month with 10,000 credits) is designed for agencies managing multiple client deployments. Each lookup or config audit consumes credits from your monthly grant.