← Case index
Case file No.063 · pypi · stdio
MCP Hangar
io.mcp-hangar/hangar · v2.32.0
Policy enforcement plane for MCP: every tool call ends in a verdict. Self-hosted, MIT.
Security score
96/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- v2.31.0 → v2.32.0Oct 21, 2026
versionchanged version bump"2.31.0" → "2.32.0"
packages.0.versionchanged package version bump"2.31.0" → "2.32.0"
- v2.29.1 → v2.31.0Oct 20, 2026
versionchanged version bump"2.29.1" → "2.31.0"
packages.0.versionchanged package version bump"2.29.1" → "2.31.0"
- v2.28.0 → v2.29.1Oct 19, 2026
versionchanged version bump"2.28.0" → "2.29.1"
packages.0.versionchanged package version bump"2.28.0" → "2.29.1"
- First snapshot (v2.28.0)Oct 16, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs MCP Hangar safe?
MCPWatch gives MCP Hangar a heuristic security score of 96/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does MCP Hangar have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package mcp-hangar. That is not proof of safety.
When was MCP Hangar last updated?
The latest registry version is 2.32.0, published Oct 20, 2026. The last push to mcp-hangar/mcp-hangar was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.
What license does MCP Hangar use?
GitHub reports the license of mcp-hangar/mcp-hangar as MIT.