MCP GET 405: what it proves, and how to test the right transport
By wicketwarden, with an AI assistant · Published
An MCP URL returns 405 Method Not Allowed to GET. That observation alone does not tell you whether its MCP requests work. Start with the protocol revision and the operation you actually need.
Why a working MCP server can reject GET
In the 2025-11-25 Streamable HTTP transport, clients send JSON-RPC messages using POST. A separate GET stream is optional; a server can answer that GET with 405 when it does not provide the stream.
The 2026-07-28 transport removes the GET stream and protocol-level sessions. Its backward-compatibility guidance recommends 405 for GET or DELETE traffic from older clients on a server supporting only that revision. A generic GET probe cannot distinguish these implementations from a route that simply rejects GET.
| Observed result | Supported conclusion | Still unknown |
|---|---|---|
| GET returns 405 | This request was refused for its method | POST handling, supported revision, authentication and useful tools |
| POST returns a JSON-RPC error | Inspect the error and requested revision | Successful completion of the intended operation |
| A declared read-only MCP request returns its expected result | That bounded request worked in this environment | Other tools, writes, payment and other environments |
A bounded diagnostic procedure
- Read the service's current transport and authentication instructions. Record the exact endpoint and revision; do not infer either from a path named
/mcp. - Declare one permitted, read-only operation and its expected response before sending it. Check that the request does not create an account, execute a tool or spend money.
- Use the lifecycle for that revision. The 2025-11-25 lifecycle starts with initialization and version negotiation. Do not copy that exchange indiscriminately into a newer client.
- For Streamable HTTP, support both JSON and SSE responses. The 2026 revision additionally requires matching protocol metadata in the header and body, plus method metadata headers. Use its current request format rather than changing a version string in an old example.
- Record the method, revision, authentication state, status, content type and expected response property. Keep a request identifier or public receipt when available. Stop on a refusal; report it without trying another identity or network.
What our field sample established
Our November 7, 2026 follow-up of 28 agent-service invitations included two MCP URLs returning 405 to GET. We left their MCP operation untested. We did not send initialization or a tool request, and the status did not justify calling either integration working or broken.
This is the useful distinction in a bug report: “GET returned 405; POST protocol untested” preserves the next test. “Service down” discards it.
Read the dated service records, or inspect open rerun requests before choosing one bounded check. A signed key identifies a statement, not an independent operator.