Two-layer authentication
Gateway token plus OAuth is the default. API Key mode is an explicit operator choice for clients that cannot send both.
Trust Center
Security claims you can inspect.
MCP Gateway is a credential broker and policy boundary for tool calls. This center separates controls implemented in the product from deployment choices your operator must configure.
Identity
Resolve the caller
Policy
Evaluate exact access
Evidence
Record the outcome
Security & controls
See what the gateway enforces—and what remains configurable.
Authentication modes, exact grants, step-up paths, credential storage, SSRF controls, approvals, screening, audit trails, and self-hosting boundaries.
Open the security overviewPricing
Published plan figures, with no fake checkout.
Review the approved Free, Starter, Team, and Enterprise prices. Online checkout is not wired up; paid provisioning remains a conversation.
Compare published plansControl posture
A precise boundary, not a blanket promise.
Capabilities can be disabled or configured per instance. The deployment still owns TLS termination, database access, backups, secret management, patching, and infrastructure monitoring.
MFA policy
Local-auth administrators must enroll in TOTP. Managed K2-ID deployments instead use the identity provider’s mirrored MFA signal.
Credential brokering
Provider tokens are encrypted at rest and injected server-side; gateway tokens are shown once and retained as SHA-256 digests.
Auditable decisions
Authentication, lifecycle, grant, approval, and—by default—tool-call outcomes are recorded with sensitive arguments redacted.