{"version":"2.1.232","anchor":"mcp-capability-probe-no-longer-hangs-on-a-bad-reply","canonical_anchor":"mcp-capability-probe-no-longer-hangs-on-a-bad-reply","heading":"MCP capability probe no longer hangs on a bad reply","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/mcp-capability-probe-no-longer-hangs-on-a-bad-reply","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### MCP capability probe no longer hangs on a bad reply\n\nAn MCP server replying badly to the capability probe no longer hangs your connection.\n\n**What**\n\nWhen probing an HTTP MCP server for discovery support, a reply carrying the wrong request id or one that fails to decode now resolves cleanly and the server is treated as predating the discovery protocol, instead of hanging or throwing.\n\n**Details**\n\n- Outcomes are reported as `id-mismatch` or `malformed`; the synthesised errors are named `McpProbeIdMismatchError` and `McpProbeMalformedReplyError`.\n- Decode failures cover both malformed JSON and schema validation failures.\n- Quoted values in the errors are cut at roughly 200 characters with a `\u2026 [truncated]` marker.\n- A stream ending early is now distinguished from a send failure via a dedicated stream-end callback.\n\n**Evidence**\n\n`McpProbeIdMismatchError`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}