Wrong Content-Type

wrong-content-type · Transport & framing

Endpoint (Streamable HTTP)

https://chaos-mcp.thomascdnns.com/s/wrong-content-type/mcp

On the wire — recorded from a real request

Symptom

what you'll observe

Strict clients reject the response; some hang waiting for a stream.

Cause

what this reproduces

Handler writes correct JSON-RPC but never sets Content-Type, so it defaults to text/plain.

Fix

how you'd resolve it

Set Content-Type: application/json (or text/event-stream when streaming).

Try it with curl

bash

curl -sS -X POST \
  https://chaos-mcp.thomascdnns.com/s/wrong-content-type/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2024-11-05",
      "capabilities": {},
      "clientInfo": {"name": "curl", "version": "1"}
    }
  }'