all scenarios

Missing capabilities

missing-capabilities · Protocol negotiation

Endpoint (Streamable HTTP)
https://chaos-mcp.thomascdnns.com/s/missing-capabilities/mcp
On the wire — recorded from a real request
your clientchaos-mcp01initializePOST /s/missing-capabilities/mcp200 OK · application/json · 2 ms"jsonrpc""2.0""id"1"result""protocolVersion""2024-11-05""serverInfo""name""chaos-mcp/missing-capabilities""version""1.0.0""instructions""chaos-mcp scenario: missing-capabilities — Missing capabilities"02tools/listPOST /s/missing-capabilities/mcp200 OK · application/json · 2 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

Client thinks the server supports nothing; tools/list is never attempted.

Cause

what this reproduces

initialize result omits the capabilities object entirely.

Fix

how you'd resolve it

Always include capabilities (at least {"tools":{}}) in the initialize result.

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

'