Is MCP Registry safe to use?

MCP Registry has an HVTrust score of 67.7/100 (Grade B), ranked #181 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Registry?

MCP Registry scores 67.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 7.2k GitHub stars and is categorized under Protocols & Tool Integration.

MCP Registry

modelcontextprotocol/registry

A community driven registry service for Model Context Protocol (MCP) servers.

Protocols & Tool Integration Go Grade B Listed NOASSERTION

67.7/100

Rank #181 of 1308

Compare MCP Registry

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-12 · 7d ago

Recent change

Rank +2

Is MCP Registry safe? MCP Registry scores 67.7/100 (Grade B), ranked #181 of 1308 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-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#12 Context7 — 68.7 (B) → #13 Microsoft MCP Catalog — 68.3 (B) → #15 MCP Specification — 67.5 (B) → #16 GitHub MCP Server — 66.7 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-19

Rank Moved

Rank dropped 11 spots (#170 → #181)

2026-08-17

Rank Moved

Rank rose 11 spots (#180 → #169)

2026-08-13

Rank Moved

Rank dropped 12 spots (#157 → #169)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for MCP Registry View Protocols & Tool Integration Report missing data

78.3

Activity sub-score · out of 100

#14

In Protocols & Tool Integration

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

2026-08-11 2026-08-19

Activity & Reach

Stars

7.2k

Forks

950

Last Push

2026-08-12

7 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

Open Issues

Rank Change

▼11

was #170

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

67.7 / 100 · 100.0% confidence

MCP Registry Protocols & Tool Integration average (58 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.6 / 25

6.1 above avg 8.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.9 below avg 11.7

Transparency50% declared license · 50% OSSF Scorecard

15.0 / 17

3.6 above avg 11.4

Maintenance60% last-push freshness · 40% commit activity

17.0 / 20

3.1 above avg 13.9

AdoptionLog-scaled stars · package downloads

9.3 / 20

1.0 below avg 10.3

Activity Inputs

78.3 / 100

StarsRepository reach

23.1 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

17.2 / 25

CommunityFork signal

13.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.7 / 10

OpenSSF Scorecard · scanned Aug 18, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 4

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 9

Maintained 10

Packaging 10

Pinned-Dependencies 7

SAST 6

Security-Policy 10

Signed-Releases 8

Token-Permissions 0

Vulnerabilities 6

Is MCP Registry safe?

MCP Registry has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Registry publish package provenance?

No published build provenance is currently detected for MCP Registry. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does MCP Registry have an OpenSSF Scorecard?

MCP Registry has an OpenSSF Scorecard score of 7.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is MCP Registry actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does MCP Registry use?

MCP Registry ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Registry's commits signed?

100% of the last 100 commits to MCP Registry are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

medium confidence

Implemented

MCP Registry appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Postgres

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-08-19

Rank Moved

Rank dropped 11 spots (#170 → #181)

2026-08-17

Rank Moved

Rank rose 11 spots (#180 → #169)

2026-08-13

Rank Moved

Rank dropped 12 spots (#157 → #169)

2026-08-08

Rank Moved

Rank dropped 22 spots (#133 → #155)

2026-07-13

Rank Moved

Rank dropped 16 spots (#96 → #112)

2026-07-11

Rank Moved

Rank rose 10 spots (#110 → #100)

2026-07-09

Grade Changed

Trust grade C → B

2026-06-25

Grade Changed

Trust grade C → B

2026-06-25

Rank Moved

Rank rose 11 spots (#131 → #120)

2026-06-24

Grade Changed

Trust grade B → C

2026-06-24

Rank Moved

Rank dropped 11 spots (#120 → #131)

2026-06-10

Grade Changed

Trust grade C → B

2026-06-07

Grade Changed

Trust grade B → C

2026-05-29

HVTrust Changed

HVTrust up 9.9pts (57.5 → 67.4)

2026-05-28

Activity Score Changed

Activity score up 21pts (61 → 82)

2026-05-27

Scorecard Added

OSSF Scorecard: 6.5/10

2026-05-27

Grade Changed

Trust grade D → C

2026-05-27

HVTrust Changed

HVTrust up 30.7pts (25.2 → 55.9)

2026-05-25

Newly Listed

First tracked at rank #100

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-registry.svg)](https://hvtracker.net/agents/mcp-registry)
            
HTML:
            <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

Data sources
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.3 · Raw JSON