Token-gated delay you set live

controlled-delay · Status & reliability

Endpoint (Streamable HTTP)

https://chaos-mcp.thomascdnns.com/s/controlled-delay/mcp

This endpoint requires a token: send Authorization: Bearer chaos-demo-token on every request, handshake included. Without it you get 401 + WWW-Authenticate: Bearer, and the attempt is logged on /control with the reason. That page also shows and rotates the token, sets the delay, and queues one-shot delays for the next requests. Add ?key=<name> to keep your own profile (with its own token). The token is a test fixture, not a secret — it is printed on a public page.

On the wire — recorded from a real request

Symptom

what you'll observe

401 until your client sends a bearer token on every request; then whatever delay you dial in at /control — instant now, 10s on the next attempt, or no answer at all.

Cause

what this reproduces

Reproduces a server whose latency changes between connections — warm vs cold cache, a dependency that degrades mid-session, a first call that beats the timeout and a retry that doesn't — behind the auth every real deployment puts in front of it.

Fix

how you'd resolve it

Attach credentials to every request, not just initialize; set an explicit per-request timeout and test both sides of it; never assume the last call's latency.

Try it with curl

bash

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