1. 400 MissingSessionID. Some clients call /chat/completions-style endpoints
directly and skip the session handshake. The MCP endpoint expects the protocol handshake; if you
are hand-rolling requests, send initialize first and keep the session header the server returns.
2. 405 on GET. GET /mcp/public/ is not a valid verb — the endpoint speaks JSON-RPC over
POST. A GET is treated as an attempt to open a server-sent-events stream that we do not offer in
this stateless deployment. Use POST with Accept: application/json, text/event-stream.
3. 404 on /mcp/public versus /mcp/public/. Both forms are served, but a proxy in front of
you may normalise one into the other and drop the body on redirect. Pin the exact URL with the
trailing slash.
4. 406 or an empty body. Send Content-Type: application/json on POST and ask for JSON in
Accept. A client that only advertises text/event-stream will be served, but a client that
advertises neither is rejected.
If your tool name comes back as unknown, check the name against tools/list — we see attempts to
call tools that were never advertised (for example automatic auth probes named
__verifymcp_auth_probe_*), and those correctly fail.