{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-the-mcp-http-transport-accept-a-token-minted-for-a-sibling-resource-oauth-resource-binding-token-audience-restriction-and-repl",
  "title": "Why does an instance of the MCP HTTP transport accept a token minted for a sibling resource: OAuth resource binding, token audience restriction, and replay defense at the boundary",
  "date_of_record": "2026 November 15",
  "scope": "Applies to MCP servers exposing HTTP-native transport (Streamable HTTP / SSE) that validate bearer tokens issued by an external authorization server using OAuth 2.1 resource indicators (RFC 8707) and audience restriction (RFC 9068). Does not apply to stdio transport, mTLS-only deployments, or tokens validated exclusively by an in-process authorization server that mints and consumes its own tokens under a single tenant.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-the-mcp-http-transport-accept-a-token-minted-for-a-sibling-resource-oauth-resource-binding-token-audience-restriction-and-repl.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-the-mcp-http-transport-accept-a-token-minted-for-a-sibling-resource-oauth-resource-binding-token-audience-restriction-and-repl.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-the-mcp-http-transport-accept-a-token-minted-for-a-sibling-resource-oauth-resource-binding-token-audience-restriction-and-repl.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2281,
    "python_slice_tokens": 394,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct questions a resource server can ask about a bearer token, and they are routinely conflated in MCP transport implementations: 1. **Is this token valid?** — signature, issuer, expiry, not-before, revocation status. 2. **Is this token valid *for me*?** — the `aud` claim, and the resource indicator bound at authorization time, must designa...",
    "what_was_observed": "A deployment of three MCP servers — `mcp-files`, `mcp-db`, `mcp-code` — behind a shared authorization server. Each server was a separate HTTP endpoint with a distinct resource indicator (`https://mcp-files.internal/`, etc.). A client obtained a token with `resource=https://mcp-files.internal/` and presented it to `mcp-db`. The request succeeded. Root cause: the `mcp-db` token verifier called a JWKS-based validation r...",
    "condition_of_validity": "The `aud`-based binding check is only meaningful when all of the following hold: - The authorization server honors the `resource` parameter (RFC 8707) and encodes it into `aud`. If the AS ignores `resource` and issues a single static audience, the resource server cannot distinguish sibling resources by `aud` alone; it must fall back to a scope or a custom cl...",
    "decision_boundary": "The decision boundary is: **does the verifier compare the token's audience to the resource server's own identifier, and does it fail closed on mismatch?** The correct behavior is to fail closed. The common incorrect behavior is to treat `aud` as advisory and validate only signature and expiry, on the reasoning that \"the issuer is trusted and the client is au...",
    "operational_effect": "The practical effect of getting the binding check wrong is lateral movement within the MCP trust domain: a token minted for a low-privilege filesystem server is accepted by a database server, and the database server's tool surface becomes reachable to a client that was never authorized for it. Because MCP tools are often stateful and side-effecting (write fi..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "9cd5d8a8568b43d68c89d4bfd8e5b61d7e92506360212a7251daddf90416df72",
    "verified_classes": [
      "ResourceBindingError",
      "ReplayWindowExceededError",
      "TokenClaims",
      "ResourceServerConfig"
    ],
    "verified_functions": [
      "validate_token_for_resource",
      "handle_mcp_request"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "ReplayWindowExceededError",
      "ResourceBindingError"
    ],
    "sample_fail_closed_invariants": [
      "token carries no audience claim; refusing to accept an unbound token",
      "sender-constrained tokens are required by policy, but this token is a plain bearer token"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
