Rank, 14 days: 229 on the Claude Code sheet
2 people reported

All time, since Sep 30.

MCP discovery URL malformed

“InvalidHTTPResponse fetching "https://mcp.hostinger.com.well-known/oauth-protected-resource"”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/605/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Remote MCP OAuth discovery URL missing slash before .well-known. Connecting to an HTTP MCP server at a bare origin fails with InvalidHTTPResponse because the discovery request joins host and .well-known without a separator.

Is this your bug?

File my report
Where
MCP OAuth discovery
Error text
InvalidHTTPResponse fetching "https://mcp.hostinger.com.well-known/oauth-protected-resource"
Versions
2.1.317
Platforms
Windows
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. OAuth discovery builds malformed URL for remote MCP server (missing / before .well-known)#106992
  2. Sanity MCP server fails to connect — malformed .well-known discovery URL (missing /)#98482

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.