MCP VERIFY

Know which MCP servers your agents can use — and enforce the decision.

Verify continuously validates MCP servers, turns fresh evidence into trust decisions, and preserves the evidence behind every approval, denial, and runtime change.

Search MCP servers Explore TrustOps Claim your server

Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage • Compare any 2-4 servers with /compare?server=namespace/name
More: About • Changelog • Status • Gateway • Compare • Trust Index • Badges • Profiles • Security • MCP API • Shortlists • Digests • RSS • RSS XML • Discovery sources • Scan my server • Submit repo • GitHub Action
HOW VERIFY WORKS

Discover → Verify → Decide → Enforce → Prove

Verify continuously validates MCP servers, turns fresh evidence into trust decisions, carries those decisions into runtime enforcement, and preserves the evidence behind every approval, denial, and change.

1
Discover
Find public and private MCP inventory.
2
Verify
Continuously validate runtime, identity, security, compatibility, and operational evidence.
3
Decide
Turn evidence into trust scores, verdicts, policies, and approval requirements.
4
Enforce
Carry decisions into runtime execution through APIs, mandates, hosting, and gateway controls.
5
Prove
Maintain evidence, validation history, decision history, and audit-ready records.
PUBLIC COVERAGE

Coverage stats

Public MCP inventory is enormous. Only a small portion currently produces fresh evidence suitable for governed adoption — that narrowing is the problem Verify exists to solve, not a gap in coverage.

Discovered candidates
81374
Repository, registry, package, code-search, and submitted candidates in the public inventory.
Endpoint on record
70043
Has a remote MCP endpoint recorded to validate against.
Opted out
105
robots.txt disallows validation. Listed with provenance only -- no score or verdict is published.
Validated at least once
274
Has completed at least one validation attempt, regardless of outcome.
Handshake + tools succeeded
204
Completed the MCP handshake and returned a tool list on its most recent attempt.
Healthy
189
Currently healthy: handshake, tools, and OAuth metadata consistency all check out.
Fresh
189
Healthy and validated within the current 24h freshness window.
Strong live candidates
12
Healthy public candidates with Verify score ≥70, at least one tool, validated in the last 48h. Paid status never boosts this count.
Coverage snapshot: Aug 11, 2026 04:41:27 PM UTC
Evaluate
Find strong candidates
Search by name, namespace, use case, client fit, freshness, OAuth, and score.
Govern
Export policy
Turn server evidence into policy, routing, decision, mandate, and ledger controls.
Research
MCP Trust Index
Public index of MCP trust signals, freshness, authenticated behavior, write safeguards, and buyer-ready adoption guidance.
Publish
Claim a server
Attach verified ownership, revalidate, publish badges, and monitor drift.
Developer workflow
MCP Verify Action
Add a pull-request check that fetches Verify policy and fails when an MCP server is blocked or below threshold.
Fresh trusted index
Fresh scores
Use fresh, confidence-weighted evidence for buyer decisions and keep stale long-tail inventory visibly separated.
Operational status
Status and backfill
Crawler, validation freshness, backfill, RSS, and route health details live off the main decision page.
Remote endpoint
https://verify.sentinelsignal.io/mcp
Public read-only MCP surface with a server card at /.well-known/mcp/server-card.json.
Metadata-only servers hidden Show
Showing 0 of 81374 indexed servers
Compare selection
No servers selected
Compare actions

Indexed servers

Indexed MCP server results with status, score, transport, tools, and OAuth signals
CompareServerStatusScoreTransportToolsOAuthEvidence age
No servers found.
MISSING FROM VERIFY?
Submit a GitHub repo for FQXCS/db-mcp
Add a repository to the MCP discovery review queue, then claim the server profile to add evidence, badges, monitoring, and revalidation.

New servers discovered (last 24 hours)