·MCP OAUTH 2.1
Spec-compliant.
Out of the box.
Four RFCs. A complete OAuth 2.1 authorization server. Your MCP tool server gets real token issuance, discovery, and scope enforcement. Not a bearer-token shim.
Most MCP servers don't actually do OAuth
Bearer tokens aren't authorization.
A token without audience binding, scopes, or discovery is just a long password.
RFC 9728
Discovery built in.
Clients hit /.well-known/oauth-authorization-server once. They learn every endpoint, scope, grant type, and challenge method you support. Zero out-of-band config.
RFC 8707
Audience-bound tokens.
Every token includes a resource indicator. A token minted for Notion's MCP cannot be replayed against yours. The tool server verifies `aud` on every call.
PKCE S256
Auth code flow. No shortcuts.
Authorization code + PKCE S256 is the only interactive grant. Implicit flow is blocked at the protocol level. No way to accidentally ship an insecure flow.
FULL AUDIT
Every call, logged.
Token issuance, refresh, tool invocation, audience mismatch, and revocation all write to an immutable audit stream. Export to your SIEM. Query by client or subject.
Wire your MCP server in one import.
One adapter between your tool server and any MCP client. OAuth 2.1 just works.
RFC 9728 · 8707 · 8414 · 7591 · PKCE S256 · MIT licensed