{
  "id": 9561323,
  "title": "OAuth on MCP is not the same as authorizing each tool call",
  "url": "https://urgent.news/2026/09/24/oauth-on-mcp-is-not-the-same-as-authorizing-each-tool-call",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-24T13:40:21.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/authbyexample1/oauth-on-mcp-is-not-the-same-as-authorizing-each-tool-call-1j09"
  },
  "original_language": "en",
  "account": null,
  "summary": "OAuth on MCP answers “who is calling?” It does not, by itself, answer whether a particular tools/call should run. The 2026-07-28 MCP spec tightens auth and routing with issuer validation, the CIMD direction, and Mcp-Method / Mcp-Name headers. Those are useful signals, but authentication is still only one decision: AuthN verifies who is calling; tool-call authorization asks whether this principal…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}