About this integration
Policy enforcement plane for MCP: every tool call ends in a verdict. Self-hosted, MIT.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 2.20.0
- Package
- mcp-hangar
- Last compatibility test
- Not independently tested
Connect your agent
mcp-hangarDocumentation-only review; package, upstream servers, auth providers, and policy paths were not executed or security-audited.
Capabilities: Mediate and authorize MCP tool calls, Pin tool schemas and enforce egress policy, Gate calls on human approval, Export attributable audit and observability data
Connected profiles
Additional details
io.mcp-hangar/hangar
Source ↗ · Checked 2026-09-172.20.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17mcp-hangar
Source ↗ · Checked 2026-09-192.21.0
Source ↗ · Checked 2026-09-19The documented serve command runs Hangar as a local stdio MCP front door from a YAML configuration; HTTP mode is separately available.
Source ↗ · Checked 2026-09-19For stdio, the spawning process is the trust boundary and auth.stdio.principal declares the caller; that configured-principal model is outside the native authentication/setup taxonomy.
Source ↗ · Checked 2026-09-19This eligibility update retains the existing stdio connection and describes the documented mcp-hangar serve command, not an HTTP endpoint.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19