updated 2026-08-12 05:02 UTC

MCP Hub

ravitemer/mcp-hub

A centralized manager for Model Context Protocol (MCP) servers with dynamic server management and monitoring

Protocols & Tool Integration JavaScript Grade D Listed MIT
23.9/100
Rank #870 of 1283
Compare MCP Hub

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

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2025-10-24 · 292d ago
Recent change
New

Is MCP Hub safe? MCP Hub scores 23.9/100 (Grade D), ranked #870 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 2% of recent commits are signed; last pushed 2025-10-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#44 mcphub — 25.5 (D) → #45 mcp-gateway-registry — 24.8 (D) → #47 arcade-mcp — 23.4 (D) → #48 MCP Java SDK — 23.3 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #870
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 292 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for MCP Hub View Protocols & Tool Integration Report missing data
24.8
Activity sub-score · out of 100
#46
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 292 days ago — may be stale

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
514
Forks
66
Last Push
2025-10-24
292 days ago
Commits (4 wk)
0
Downloads (7d)
781
npm
HN mentions (30d)
—
Open Issues
12
Rank Change
▲1
was #871

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

23.9 / 100 · 67.0% confidence

MCP Hub Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
8.5 below avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.9 below avg 11.4
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.8 below avg 13.8
AdoptionLog-scaled stars · package downloads
10.4 / 20
in line with avg 10.4

Activity Inputs

24.8 / 100
StarsRepository reach
16.3 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
8.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
2%
of last 100 commits verified

Is MCP Hub safe?

Public trust evidence for MCP Hub is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MCP Hub publish package provenance?
No published build provenance is currently detected for MCP Hub. 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 Hub have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MCP Hub. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is MCP Hub actively maintained?
Stale. The repository has not been pushed to in 292 days. Consider whether the project is still being maintained.
What license does MCP Hub use?
MCP Hub ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Hub's commits signed?
2% of the last 100 commits to MCP Hub 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
high confidence
Implemented
MCP Hub 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.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
medium confidence
Marketplace
Marketplace plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Hub?

For maintainers

HVTrust scores MCP Hub 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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #870
GitHub → npm: mcp-hub

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 23.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-hub.svg)](https://hvtracker.net/agents/mcp-hub)
HTML:
<a href="https://hvtracker.net/agents/mcp-hub"><img src="https://hvtracker.net/badge/mcp-hub.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON