MCP OAuth resource indicator — real app HTTP capture
Side: before | Commit: 6f21b0f02a8e128374e2a44a48f8b45b270be9f7
Environment: Linux; full T3 dev server; fresh isolated database; no seed
Transport: loopback HTTP; no mocked services; redirects not followed
GET /.well-known/oauth-protected-resource/mcp -> 200
POST /oauth/mcp/register -> 201 (synthetic loopback client)

GET /oauth/mcp/authorize with resource=http://127.0.0.1:14514/mcp
  HTTP 302
  Location: /connect-agent?... (approval continues; error absent)
  Observed: accepted

GET /oauth/mcp/authorize with resource=http://127.0.0.1:14514/mcp#section
  HTTP 302
  Location: http://localhost:51234/callback?error=invalid_target&error_description=This+server+only+issues+tokens+for+http%3A%2F%2F127.0.0.1%3A14514%2Fmcp.&state=evidence-state
  Observed: invalid_target

GET /oauth/mcp/authorize with resource=/mcp
  HTTP 302
  Location: http://localhost:51234/callback?error=invalid_target&error_description=This+server+only+issues+tokens+for+http%3A%2F%2F127.0.0.1%3A14514%2Fmcp.&state=evidence-state
  Observed: invalid_target

GET /oauth/mcp/authorize with resource=https://other.example/mcp
  HTTP 302
  Location: http://localhost:51234/callback?error=invalid_target&error_description=This+server+only+issues+tokens+for+http%3A%2F%2F127.0.0.1%3A14514%2Fmcp.&state=evidence-state
  Observed: invalid_target

GET /oauth/mcp/authorize with resource=http://127.0.0.1:14514/mcp#
  HTTP 302
  Location: /connect-agent?... (approval continues; error absent)
  Observed: accepted

Observed results: {"canonical": "accepted", "emptyFragment": "accepted", "nonemptyFragment": "invalid_target", "otherAudience": "invalid_target", "relative": "invalid_target"}
Empty fragment ACCEPTED; defect reproduced