NEED_REVIEW Is Not a Failure: What 5,394 Rows of Uncertainty Show
The public Registry has 5,394 NEED_REVIEW rows. This is not inspection failure; it is an explicit state for missing evidence that matters to adoption.
Terminology
| Term | Meaning |
|---|---|
| Public Registry | Inspected MCP candidates searchable in the public Registry |
| Profile evidence | Inspection-profile aggregates used to interpret public candidates in more depth |
| Review/action rows | Entries in WARN, NEED_REVIEW, RESTRICT, or BLOCK that require reasoned adoption review |
Lead
If NEED_REVIEW is hidden as a generic failure, adopters miss uncertainty. Making it explicit tells reviewers what evidence still needs to be gathered.
Key Findings
- The public Registry has 5,394 NEED_REVIEW rows. This is not inspection failure; it is an explicit state for missing evidence that matters to adoption.
- The 20,629 public Registry entries and 11,627 profile-evidence rows answer different questions and should not be mixed casually.
- The observation is an adoption input, not a final approval for a specific environment.
- Counts are snapshot evidence, so adoption review should check the observation date before treating the number as current state.
Dataset
| Item | Value |
|---|---|
| Article date | 2026-05-23 |
| Public Registry snapshot | 20,629 entries, synced 2026-06-06T01:17:38.963Z |
| Detailed profile evidence | 11,627 rows, generated 2026-05-20/21 |
| Public disclosure level | Aggregates, distributions, anonymized observations, and operational interpretation |
Observed Metrics
| Metric | Value | Meaning |
|---|---|---|
| Public NEED_REVIEW rows | 5,394 | Public candidate needing additional review |
| Local NEED_REVIEW profiles | 2,068 | Profile-evidence candidate needing additional review |
| Repository not found | 1,290 | One major reason for NEED_REVIEW |
What We Observed
If NEED_REVIEW is hidden as a generic failure, adopters miss uncertainty. Making it explicit tells reviewers what evidence still needs to be gathered. This lens matters because MCP servers are not just plugins; they are bundles of authority exposed to an AI agent.
Practical Reading
Treat NEED_REVIEW as a queue segmented by missing provenance, authentication, runtime execution, or configuration evidence. Review should record execution location, destinations, data touched, and unresolved evidence, not only the server name or README.
Limits
- The evidence uses public aggregate data and anonymized observations, not internal detection mechanics.
- Counts are snapshot values and will change as the Registry updates.
- This is not a claim that any named MCP server is safe or unsafe.
Conclusion
Treat NEED_REVIEW as a queue segmented by missing provenance, authentication, runtime execution, or configuration evidence. Keeping this evidence in the intake record makes the review repeatable across teams and deployments.
MCP Guard continuously turns public Registry and profile evidence into adoption-review signals for MCP security teams.