MCP authorization: Authorization (draft)
Provision mcp.12 · Model Context Protocol, Authorization (draft) · requirement
MCP servers MUST NOT accept or transit any other tokens.
The text is as taken from the source. In the source: https://modelcontextprotocol.io/specification/draft/basic/authorization#token-handling (the section of the specification that holds the requirement (its opening words were found there); linked 2026-11-10). The instrument: Model Context Protocol, Authorization (draft), the project's; requirements quoted with the source; read 2026-11-09.
Who cites it
| Indicator | The fact it asks for | Kind of link | The assertion |
|---|---|---|---|
I28 | Its tokens are bound to the service they were issued for and are not passed on | same: evidenced | Asserted in the mapping by gamma-ray@web-summit.dinis; the written basis is not recorded yet. |
A link is our assertion, not the instrument's. "Same" carries the evidence to the provision in full. "Part" marks the provision as partly evidenced: the fact is one piece of what it asks. "Negation" points the other way.
The evidence that reaches it
No published card reaches this provision yet. That is not a no.
Touched never means complies.
Answer it directly
A company can answer this line item itself, in its own file at /.well-known/fact-ray.json, with the node gamma-ray:provision/mcp.12 (how). A company that already assesses itself against MCP authorization can reuse that work.