all scenarios

Healthy server (control)

healthy · Baseline

Endpoint (Streamable HTTP)
https://chaos-mcp.thomascdnns.com/s/healthy/mcp
On the wire — recorded from a real request
your clientchaos-mcp01initializePOST /s/healthy/mcp200 OK · application/json · 10 ms"jsonrpc""2.0""id"1"result""protocolVersion""2024-11-05""capabilities""tools""serverInfo""name""chaos-mcp/healthy""version""1.0.0""instructions""chaos-mcp scenario: healthy — Healthy server (control)"02tools/listPOST /s/healthy/mcp200 OK · application/json · 6 ms"jsonrpc""2.0""id"2"result""tools""name""echo""description""Echo back the provided message.""inputSchema""type""object""properties""message""type""string""description""Text to echo"… 40 more lines

Symptom

what you'll observe

Everything works. Use this to confirm your client is set up correctly before testing failures.

Cause

what this reproduces

Nothing wrong — a correct Streamable HTTP MCP server with three working tools.

Fix

how you'd resolve it

—

Try it with curl
bash
curl -sS -X POST \
  https://chaos-mcp.thomascdnns.com/s/healthy/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"

'