all scenarios

One slow tool

tool-slow · Tools — execution

Endpoint (Streamable HTTP)
https://chaos-mcp.thomascdnns.com/s/tool-slow/mcp
On the wire — recorded from a real request
your clientchaos-mcp01initializePOST /s/tool-slow/mcp200 OK · application/json · 1 ms"jsonrpc""2.0""id"1"result""protocolVersion""2024-11-05""capabilities""tools""serverInfo""name""chaos-mcp/tool-slow""version""1.0.0""instructions""chaos-mcp scenario: tool-slow — One slow tool"02tools/call slow_toolPOST /s/tool-slow/mcp! no response after 3s — socket still open

Symptom

what you'll observe

Handshake and tools/list are instant, but this one tool takes ~40s and times out.

Cause

what this reproduces

A single expensive operation with no timeout or progress reporting.

Fix

how you'd resolve it

Add per-tool timeouts; report progress; return a job id for long work.

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

'