Mcp
Table of Contents
Classes
- BearerChallengeError
- The three RFC 6750 §3.1 error codes a `WWW-Authenticate: Bearer` challenge may name
(CONTRACT.md §28.4) — the complete vocabulary; nothing else, not even a well-formed
OAuth error code such as `invalid_grant`, is accepted by {@see Mcp::bearerChallenge()}.
- Mcp
- MCP resource-server helpers (CONTRACT.md §28, RFC 9728 + RFC 6750) — the ONE §28
implementation both {@see \Axiam\Sdk\Laravel\AxiamMiddleware} and
{@see \Axiam\Sdk\Symfony\AxiamAuthSubscriber} are built on, mirroring how this SDK
never duplicates a security-critical decision across its two framework bridges (D-02).
- McpGuardOptions
- Validates a §10 guard's CONTRACT.md §28.5 configuration and precomputes the challenge
values it will emit, at guard-CONSTRUCTION time so that an invalid one is a startup
failure rather than a surprise on the 401 path — the same discipline
{@see \Axiam\Sdk\AxiamClient}'s own constructor applies to every other CONDITIONAL
option.
- ProtectedResourceMetadata
- What {@see Mcp::protectedResourceMetadata()} returns: the RFC 9728 §2 document, the
path it is served at, and the URL that path resolves to (CONTRACT.md §28.1).