all scenarios

OAuth discovery dead-end

oauth-dead-discovery · Auth & OAuth

Endpoint (Streamable HTTP)
https://chaos-mcp.thomascdnns.com/s/oauth-dead-discovery/mcp
On the wire — recorded from a real request
your clientchaos-mcp01initializePOST /s/oauth-dead-discovery/mcp401 Unauthorized · application/json · 1 ms"jsonrpc""2.0""id"null"error""code"-32001"message""authentication required; see WWW-Authenticate"WWW-Authenticate: Bearer resource_metadata="https://chaos-mcp.thomascdnns.com/.well-known/oauth-…tools/list answers identically — every request does

Symptom

what you'll observe

Client begins OAuth, fetches the advertised metadata URL, and gets 404. Auth can't proceed.

Cause

what this reproduces

WWW-Authenticate points at /.well-known/oauth-protected-resource but that endpoint isn't served.

Fix

how you'd resolve it

Actually serve the protected-resource and authorization-server metadata documents.

Try it with curl
bash
curl -sS -X POST \
  https://chaos-mcp.thomascdnns.com/s/oauth-dead-discovery/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '
"jsonrpc""2.0"
"id"1
"method""initialize"
"params"
"protocolVersion""2024-11-05"
"capabilities"
"clientInfo""name""curl""version""1"

'