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

All time, since Oct 29.

MCP name constraint failure

“Failed to reconnect to <server>: UNSUPPORTED_CONSTRAINT_TYPE at https://127.0.0.1:<port>”

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/23140/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

HTTPS MCP connection fails when CA has IP-address Name Constraint. Connection to an HTTP MCP server is refused when its certificate chains to a CA with a critical Name Constraints extension containing an IP subtree.

Is this your bug?

File my report
Where
MCP HTTP transport
Error text
Failed to reconnect to <server>: UNSUPPORTED_CONSTRAINT_TYPE at https://127.0.0.1:<port>
Versions
2.1.314 to 2.1.323. Still reported on the newest version, 2.1.323.
Platforms
Windows
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. HTTP MCP connection fails with "UNSUPPORTED_CONSTRAINT_TYPE" when the CA has an IP-address Name Constraint (Node.js accepts the same chain)#109500
  2. MCP HTTPS: a trust anchor with an iPAddress name constraint fails with UNSUPPORTED_CONSTRAINT_TYPE (NODE_EXTRA_CA_CERTS is honoured)#106100

Do you work on Claude Code?

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