The MCP ecosystem often has several independent packages implementing the same tool — and "Registry" currently has 9. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.
| Implementation | Package | Trust | Capability | Coverage | Findings | Scanned |
|---|---|---|---|---|---|---|
| Registry Officialbest by github | @github/mcp-registry
npm |
A 100/100 | Minimal | Source | 0 | 2026-10-08 |
| Registry by uluops | @uluops/registry-mcp
npm |
A 99/100 | Minimal | Source | 0 | 2026-10-08 |
| Registry by mdfifty50-boop | mcp-registry-mcp
npm |
A 99/100 | Minimal | Source | 0 | 2026-10-08 |
| Registry by wei | mcp-registry-mcp-server
npm |
A 99/100 | Minimal | Source | 0 | 2026-10-08 |
| Mcp Registry by formulahendry | mcp-server-mcp-registry
npm |
A 99/100 | Minimal | Source | 0 | 2026-10-08 |
| Registry by npm | mcp-registry
npm |
A 98/100 | Minimal | Source | 0 | 2026-10-08 |
| Registry Source verified by foretak | registry-mcp
npm |
A 94/100 | High | Source | 1 | 2026-10-08 |
| Registry by foretak | registry-mcp
PyPI |
A 93/100 | High | Source | 2 | 2026-09-20 |
| Registry by cccntu | mcp-registry
PyPI |
A 93/100 | High | Source | 4 | 2026-09-20 |
A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.