{"version":"2.1.273","anchor":"http-method-handling-tightened-for-a-webhook-style-mcp-trans","canonical_anchor":"http-method-handling-tightened-for-a-webhook-style-mcp-trans","heading":"HTTP method handling tightened for a webhook-style MCP transport route","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/http-method-handling-tightened-for-a-webhook-style-mcp-trans","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### HTTP method handling tightened for a webhook-style MCP transport route\n\nA webhook-style connection route now replies 'method not allowed' instead of 'not found' for wrong HTTP methods\n\n**What**\n\nClaude Code has an internal route used to look up a live MCP (Model Context Protocol, the system that lets Claude use external tools) transport connection by secret and ID. If a request to a valid, known connection used the wrong HTTP method (anything other than `POST`), it used to get the same generic \"not found\" response as a request to a connection that doesn't exist at all. Now it gets a proper \"method not allowed\" response, with an `Allow: POST` header telling the caller what method it should have used.\n\n**Why**\n\nThis makes it possible to tell the difference between \"this connection doesn't exist\" and \"this connection exists but you called it the wrong way,\" which is clearer for anything talking to this route programmatically.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}