tunnel.disconnected

⚠️

Preview — this feature is being built; the design below is the spec.

Sent when: The last online connector of an MCP tunnel disconnected and stayed away for 2 minutes.

Property	Value
Scope	One workspace. Register with an inference key at `/v1/webhooks`.
Area	MCP tunnels
Subscribe with	`"events": ["tunnel.disconnected"]`, or a prefix such as `"tunnel.*"`

Payload

{
  "id": "evt_01JCA5D7F9H1K3M5P7R9",
  "type": "tunnel.disconnected",
  "created_at": "2026-11-05T10:00:00Z",
  "workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
  "data": {
    "object": {
      "id": "tnl_01JCE4G6J8L0N2Q4S6U8",
      "type": "tunnel",
      "status": "disconnected",
      "last_seen_at": "2026-11-05T09:58:00Z"
    }
  }
}

data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.

What to do

Requests and agents using the tunnel are failing with 502 tunnel_unavailable until a connector reconnects. Check the connector host.

Delivery

Deliveries are signed, retried with back-off for up to 3 days, and may arrive more than once or out of order. De-duplicate on the syntic-event-id header and compare timestamps before acting. See Webhooks.

eval.run.completed plugin.scan_failed

Was this page helpful?