updated 2026-08-17 00:02 UTC

MCP Hangar

mcp-hangar/mcp-hangar

MCP policy enforcement plane — deterministic policy on every Model Context Protocol call: identity, RFC 8707 audience bi

MCP Servers Python Grade B Listed MIT
71.6/100
Rank #127 of 1308
Compare MCP Hangar

How does it stack up against its MCP Servers 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-16 · 1d ago
Recent change
New

Is MCP Hangar safe? MCP Hangar scores 71.6/100 (Grade B), ranked #127 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 99% of recent commits are signed; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#22 Blockrun MCP — 72.0 (B) → #23 Safari MCP — 71.9 (B) → #25 Auth0 MCP Server — 71.2 (B) → #26 iOS Simulator MCP — 71.0 (B) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-16
Newly Listed
First tracked at rank #126
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Compare with another agent Get email alerts for MCP Hangar View MCP Servers Report missing data
61.1
Activity sub-score · out of 100
#24
In MCP Servers

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 →

Signals refreshed 2026-08-17 00:02 UTC · Repo last pushed yesterday

Activity & Reach

Stars
13
Forks
7
Last Push
2026-08-16
yesterday
Commits (4 wk)
359
Downloads (7d)
1,078
pypi
HN mentions (30d)
—
Open Issues
18
Rank Change
▼1
was #126

Analysis

HVTrust Dimensions vs MCP Servers

71.6 / 100 · 100.0% confidence

MCP Hangar MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.4 / 25
7.4 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
6.8 / 20
1.0 above avg 5.8

Activity Inputs

61.1 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
4.2 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
99%
of last 100 commits verified

Is MCP Hangar safe?

MCP Hangar 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 Hangar publish package provenance?
Yes. MCP Hangar's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does MCP Hangar have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for MCP Hangar. 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 Hangar actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Hangar use?
MCP Hangar ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Hangar's commits signed?
99% of the last 100 commits to MCP Hangar 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 Hangar appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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 MCP Hangar?

For maintainers

HVTrust scores MCP Hangar 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-16
Newly Listed
First tracked at rank #126
GitHub → PyPI: mcp-hangar

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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