MCP Census Verdict Triage Ladder
Treat MCP Census's four verdicts as a routing ladder rather than a binary gate.
By InnovaAI ResearchPublished
What is MCP Census Verdict Triage Ladder?
“Four verdicts, four delivery paths: PASS ships, UNKNOWN gates”
Treat MCP Census's four verdicts as a routing ladder rather than a binary gate. PASS servers go straight into a client agent stack (Claude Code, Codex, Cursor, VS Code) with the stamped evidence artifact filed in the delivery pack. REVIEW entries get a manual read of the reasons before anyone installs. BLOCK entries are removed from the .mcp.json and logged as a finding the client can see. UNKNOWN is the expensive rung: it means public evidence was thin, so an agency must either substitute a verifiable server or scope a manual review into the retainer. The economics matter here. The free tier's 1,000 credits each UTC month and the $19 builder tier's 2,000 credits cover most single-client audits, so the ladder costs almost nothing to run. What it protects is margin: one BLOCK caught before go-live is cheaper than an incident call after handover.
More on MCP Census
- StrategyWhy MCP Census Turns MCP Server Vetting Into a Billable Agency Gate
- Evaluation RuleMCP Census Rule: Gate Client MCP Servers Before Install, Not After the Incident
- Decision FrameworkMCP Census: Buy vs Skip (MCP Server Vetting for Client Agent Stacks)
- Failure PatternThe MCP Census Verdict Drift Trap: Why Agencies Fail With MCP Census in Client Agent Delivery
- Implementation BlueprintMCP Census MCP Server Vetting Gate (5-7 days)
- Operating ProcedureMCP Census Client MCP Config Audit (Onboarding)