Governed MCP Infrastructure
Dual-Role Architecture: Intelligent Gateway & Compliant Server
Anthropic's Model Context Protocol connects LLM agents to tools and data. AuthHub provides the missing enterprise security layer: front existing MCP tools with a high-throughput Zero-Trust Authorization Gateway, or deploy AuthHub as a fully compliant MCP Server with dynamic SSE streaming, adaptive tool registries, and Merkle-anchored audit trails.
AuthHub as an MCP Gateway
Acts as a secure reverse proxy and policy decision point (PDP) in front of internal or third-party MCP servers. Enforces OAuth 2.1 authentication, validates RFC 8707 audience bindings, and intercepts every tools/call with sub-5ms AuthZEN SARC evaluations.
- RFC 9728 & RFC 6750 401 Discovery Challenge Handshake
- Sub-5ms Google Zanzibar / SpiceDB relationship authorization
- Zero token passthrough — upstream credential isolation (Rule M8)
- Dynamic CAEP revocation signals push immediate SSE list changes
AuthHub as an MCP Server
Exposes a spec-compliant JSON-RPC 2.0 endpoint implementing Model Context Protocol specifications (versions 2026-07-28 through 2024-11-05). Provides persistent SSE streams, dynamic tool registration, context resources, and governed prompt templates.
- Full JSON-RPC 2.0 lifecycle: initialize, tools/list, resources, prompts
- Adaptive tool filtering based on caller identity & tenant schema
- Bidirectional SSE streaming with
Mcp-Session-Idlifecycle tracking - Immutable CockroachDB & MinIO S3 Merkle tree audit anchoring
End-to-End Model Context Protocol Topology
How clients, identity providers, AuthHub MCP Gateway, and upstream tools interact without token leakage or privilege escalation.
Initiates connection. Follows RFC 9728 401 challenge to authenticate at enterprise IdP.
Validates audience (RFC 8707). Evaluates tool call permissions in <5ms against SpiceDB graph.
Swaps client bearer token for short-lived, encrypted upstream credential. Zero passthrough.
Executes requested tool (Database, Cloud, EHR, Internal APIs). Results returned securely.
# 1. Unauthenticated client probes the MCP Gateway:
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="AuthHub", scope="authhub:authorize", resource_metadata="https://api.authhub.cloud/.well-known/oauth-protected-resource"
# 2. Authenticated tool call gated by live AuthZEN policy:
POST /mcp
Authorization: Bearer <audience-bound-token>
{"jsonrpc":"2.0","id":102,"method":"tools/call","params":{"name":"read_patient_record","arguments":{"patient_id":"101"}}}
# 3. Gateway evaluates SpiceDB relationship (physician->care_team->patient):
# PERMIT (record 101): Returns 200 with upstream sanitized clinical data
# DENY (record 999): Returns 403 Forbidden ("No matching permission found")Protocol & Standards Compliance Matrix
AuthHub complies with all normative clauses of the OpenID Foundation, IETF OAuth, and Model Context Protocol specifications.
| Specification / RFC | Title / Scope | Role | Status | Verified Mechanism |
|---|---|---|---|---|
| RFC 9728 | OAuth 2.0 Protected Resource Metadata | Gateway | Verified Live | Published at /.well-known/oauth-protected-resource |
| RFC 8707 | Resource Indicators for OAuth 2.0 (Audience Binding) | Gateway | Verified Live | Strict token audience verification prevents Confused Deputy |
| MCP 2026-07-28 | Model Context Protocol Core Specification | Server + Gateway | Production Ready | JSON-RPC 2.0 negotiation, session management, dynamic discovery |
| AuthZEN 1.0 | OpenID Authorization API (SARC Evaluation) | Gateway | 100+ Tests Passed | Inline permission checks (<5ms) mapped to SpiceDB relationships |
| RFC 8693 / ID-JAG | OAuth 2.0 Token Exchange & Cross-App Identity | Gateway | Verified Live | Swaps client token for short-lived upstream credential |
| SSF / CAEP 1.0 | Continuous Access Evaluation Profile & Shared Signals | Gateway + Server | Verified Live | Pushes notifications/tools/list_changed upon policy revocation |
Ready to inspect detailed capabilities?
Explore dedicated technical coverage pages for either MCP Gateway enforcement or MCP Server execution.