MCP Registry
A community driven registry service for Model Context Protocol (MCP) servers.
Is MCP Registry safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Registry
How does it stack up against its Protocols & Tool Integration neighbours?
Pick any agent to compare →In detail: MCP Registry scores 67.6/100 (Grade B), ranked #412 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.7/10; 100% of recent commits are signed; last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Registry could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 7.7 to 9.0lowest checks: CII-Best-Practices 0, Token-Permissions 0, Vulnerabilities 4 +2.7 → 70.3 B · #15 of 62
Chain of custody
Scanners check what the code says. This traces who ships MCP Registry and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/modelcontextprotocol/registry, NOASSERTION, last pushed 2026-10-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.7/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection8
- Signed Releases8
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies7
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 8CI-Tests 10CII-Best-Practices 0Code-Review 5Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 10License 9Maintained 10Packaging 10Pinned-Dependencies 7SAST 7Security-Policy 10Signed-Releases 8Token-Permissions 0Vulnerabilities 4 -
Published packages None
No registry package. MCP Registry is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of MCP Registry.
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions
Verify this score yourself
Every build re-issues MCP Registry’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How MCP Registry compares in Protocols & Tool Integration
- #18 GitHub MCP Server 68.1 +0.5
- #19 MCP Specification 68.0 +0.4
- #20 MCP Registry 67.6 this agent
- #21 Serena 67.3 −0.3
- #22 MCP Context Forge 66.7 −0.9
Bars show each HVTrust score; the tick marks MCP Registry’s 67.6.
Where the 67.6 comes from
HVTrust dimensions vs the Protocols & Tool Integration average
67.6 / 100 · 100.0% confidenceMCP Registry Protocols & Tool Integration average (62 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
77.8 / 100Common questions about MCP Registry
Does MCP Registry publish package provenance?
Does MCP Registry have an OpenSSF Scorecard?
Is MCP Registry actively maintained?
What license does MCP Registry use?
Are MCP Registry's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain MCP Registry?
For maintainers
HVTrust scores MCP Registry from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-registry)
<a href="https://hvtracker.net/agents/mcp-registry"><img src="https://hvtracker.net/badge/mcp-registry.svg" alt="HVTrust"></a>
Other agents in Protocols & Tool Integration
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON