Security
Identity and authorization
How MCPG establishes who a caller is and decides what they may do — a three-tier trust model, native JWT/OIDC verification, and a pre-dispatch authorization chain that fails closed.
Identity — OIDC, JWKS, mTLS, SPIFFE, API keys
Configure inbound identity. The gateway verifies JWT bearers natively; richer or chained identity loads as plugins.
Policy authorization — Cedar, OPA, Casbin
Authorize tool calls, prompts, and resources. Three policy engines plus a built-in trust floor; chain them for defense-in-depth.
Plugin security
MCPG runs every backend and extension as a verified plugin. Ed25519 signatures, SHA-256 content pinning, a revocation list, and typed fail-closed capability grants gate what loads and what it can touch. Set Enforce in production.
Audit trail
A tamper-evident, hash-chained, fail-closed compliance ledger. Every authorization decision, payment, and access attempt is recorded with actor, action, resource, and outcome, fanned out to durable sinks.
Compliance and conformance
An honest statement of MCPG's MCP protocol conformance — both supported wire versions pass the upstream third-party conformance suite on every CI run, gated as a required check.