updated 2026-09-26 06:32 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 Listed MIT

Is MCP Hub safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.8 / 10
Provenance None
Signed commits 2%
Last push 337d ago
Compare MCP Hub

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

Pick any agent to compare →
Suggest a correction

In detail: MCP Hub scores 40.5/100 (Grade D), ranked #1155 of 1325 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 2.8/10; 2% of recent commits are signed; last pushed 2025-10-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Hub compares in Protocols & Tool Integration

  1. #53 MetaMCP 43.8 +3.3
  2. #54 mcpo 41.7 +1.2
  3. #55 MCP Hub 40.5 this agent
  4. #56 MCP-Bridge 39.8 −0.7
  5. #57 MCP Playwright 36.9 −3.6

Bars show each HVTrust score; the tick marks MCP Hub’s 40.5.

Where the 40.5 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

40.5 / 100 · 100.0% confidence

MCP Hub Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.6 / 25
6.9 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
10.9 / 17
2.0 below avg 12.9
Maintenance60% last-push freshness · 40% commit activity
0 / 20
14.1 below avg 14.1
AdoptionLog-scaled stars · package downloads
10.2 / 20
in line with avg 10.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Perplexity
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 93 spots (#1253 → #1160)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.8/10. Tighten the weakest checks to improve public safety evidence.
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 337 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.7
Activity sub-score · out of 100
#55
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 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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 337 days ago — may be stale

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
521
Forks
64
Last Push
2025-10-24
337 days ago
Commits (4 wk)
0
Downloads (7d)
623
npm
HN mentions (30d)
—
Open Issues
13
Rank Change
▲6
was #1161

Analysis

Activity Inputs

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

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.8 / 10
OpenSSF Scorecard · scanned Sep 14, 2026
Signed Commits
2%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow -1
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies -1
SAST 0
Security-Policy 4
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Common questions about MCP Hub

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?
MCP Hub has an OpenSSF Scorecard score of 2.8/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 Hub actively maintained?
Stale. The repository has not been pushed to in 337 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
None detected
No clear plugin system or broad tool 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
How this surface has changed

Detected changes to MCP Hub's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Perplexity
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → none

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
Rank 19Listed 2HVTrust 2Scorecard 1Surface 1Delisted 1MCP 1Surface 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Perplexity
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 93 spots (#1253 → #1160)
2026-09-23
HVTrust Changed
HVTrust up 24.8pts (15.5 → 40.3)
2026-09-22
Newly Listed
First tracked at rank #1253
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-12
Rank Moved
Rank dropped 12 spots (#1139 → #1151)
2026-09-09
Rank Moved
Rank dropped 11 spots (#1124 → #1135)
2026-09-07
Rank Moved
Rank dropped 22 spots (#1093 → #1115)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1077 → #1093)
2026-09-05
Rank Moved
Rank dropped 41 spots (#1036 → #1077)
2026-09-04
Rank Moved
Rank dropped 25 spots (#1011 → #1036)
2026-09-03
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → none
2026-09-03
Rank Moved
Rank dropped 32 spots (#979 → #1011)
2026-09-02
Rank Moved
Rank dropped 48 spots (#931 → #979)
2026-09-01
Rank Moved
Rank dropped 35 spots (#896 → #931)
2026-08-31
Rank Moved
Rank dropped 29 spots (#867 → #896)
2026-08-30
Scorecard Added
OSSF Scorecard: 2.8/10
2026-08-30
Rank Moved
Rank rose 209 spots (#1076 → #867)
2026-08-30
HVTrust Changed
HVTrust up 15.8pts (23.9 → 39.7)
2026-08-29
Rank Moved
Rank dropped 47 spots (#1029 → #1076)
2026-08-28
Rank Moved
Rank dropped 32 spots (#997 → #1029)
2026-08-27
Rank Moved
Rank dropped 22 spots (#975 → #997)
2026-08-26
Rank Moved
Rank dropped 100 spots (#875 → #975)
2026-08-24
Rank Moved
Rank dropped 10 spots (#865 → #875)
2026-08-17
Rank Moved
Rank rose 12 spots (#887 → #875)
2026-08-16
Rank Moved
Rank dropped 22 spots (#865 → #887)
2026-08-10
Newly Listed
First tracked at rank #870
GitHub → npm: mcp-hub

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 40.5 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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON