updated 2026-10-16 16:07 UTC

MCP Hub

Repository by ravitemer

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 357d ago
Advisories None known
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.2/100 (Grade D), ranked #1212 of 1378 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; no published advisory affects its latest release (mcp-hub); last pushed 2025-10-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Hub 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Hub and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/ravitemer/mcp-hub, MIT, last pushed 2025-10-24. 2% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.8/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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

  3. Published packages Linked, not attested

    • npm mcp-hub Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-hub 4.2.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 2.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Hub’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.

Signed credential (JSON) How to verify

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 Hub compares in Protocols & Tool Integration

  1. #56 MetaMCP 42.5 +2.3
  2. #57 mcpo 40.4 +0.2
  3. #58 MCP Hub 40.2 this agent
  4. #59 MCP-Bridge 39.8 −0.4
  5. #60 MCP Playwright 36.9 −3.3

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

Where the 40.2 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

40.2 / 100 · 100.0% confidence

MCP Hub Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.6 / 25
7.3 below avg 10.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
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.2 below avg 14.2
AdoptionLog-scaled stars · package downloads
9.9 / 20
1.2 below avg 11.1

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 357 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
#58
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-10-16 16:07 UTC · Repo last pushed 357 days ago — may be stale

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
521
Forks
65
Last Push
2025-10-24
357 days ago
Commits (4 wk)
0
Downloads (7d)
354
npm
HN mentions (30d)
—
Open Issues
13
Rank Change
▼3
was #1209

Analysis

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

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 357 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.2 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.4 · Raw JSON