Hatago MCP Hub

Hatago MCP Hub is a lightweight hub server that provides unified management for multiple MCP servers.

MCP Servers TypeScript Grade D Listed MIT
37.6/100
Rank #1090 of 1320
Compare Hatago MCP Hub

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2025-09-14 · 355d ago
Recent change
Rank +5

Is Hatago MCP Hub safe? Hatago MCP Hub scores 37.6/100 (Grade D), ranked #1090 of 1320 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.9/10; 23% of recent commits are signed; last pushed 2025-09-14. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 56 spots (#1027 → #1083)
2026-09-02
Rank Moved
Rank rose 149 spots (#1176 → #1027)
2026-09-02
HVTrust Changed
HVTrust up 12.5pts (25.1 → 37.6)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/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 355 days ago. Fresh activity helps separate stable projects from stale ones.
12.3
Activity sub-score · out of 100
#622

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-04 14:03 UTC · Repo last pushed 355 days ago — may be stale

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
27
Forks
5
Last Push
2025-09-14
355 days ago
Commits (4 wk)
0
Downloads (7d)
75
npm
HN mentions (30d)
Open Issues
4
Rank Change
▼7
was #1083

Analysis

HVTrust Dimensions vs MCP Servers

37.6 / 100 · 100.0% confidence

Hatago MCP Hub MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.8 / 25
4.7 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
0.8 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.0 / 20
in line with avg 6.2

Activity Inputs

12.3 / 100
StarsRepository reach
8.7 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.6 / 20

Supply Chain Trust

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

Is Hatago MCP Hub safe?

Public trust evidence for Hatago 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 Hatago MCP Hub publish package provenance?
No published build provenance is currently detected for Hatago 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 Hatago MCP Hub have an OpenSSF Scorecard?
Hatago MCP Hub has an OpenSSF Scorecard score of 2.9/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 Hatago MCP Hub actively maintained?
Stale. The repository has not been pushed to in 355 days. Consider whether the project is still being maintained.
What license does Hatago MCP Hub use?
Hatago MCP Hub ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Hatago MCP Hub's commits signed?
23% of the last 100 commits to Hatago 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
Hatago MCP Hub appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency 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

Maintain Hatago MCP Hub?

For maintainers

HVTrust scores Hatago 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.

Reputation Timeline

Signal history
Rank 6HVTrust 2Listed 1Scorecard 1
2026-09-03
Rank Moved
Rank dropped 56 spots (#1027 → #1083)
2026-09-02
Rank Moved
Rank rose 149 spots (#1176 → #1027)
2026-09-02
HVTrust Changed
HVTrust up 12.5pts (25.1 → 37.6)
2026-09-01
Scorecard Added
OSSF Scorecard: 2.9/10
2026-09-01
Rank Moved
Rank rose 130 spots (#1306 → #1176)
2026-09-01
HVTrust Changed
HVTrust up 10.5pts (14.6 → 25.1)
2026-08-26
Rank Moved
Rank dropped 16 spots (#1273 → #1289)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1250 → #1276)
2026-08-10
Rank Moved
Rank dropped 78 spots (#1169 → #1247)
2026-08-08
Newly Listed
First tracked at rank #1170

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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