TRtraversal

Get Mcp Harnesses

Changed on

Every harness the caller has connected to Traversal MCP from.

The organization and user are always the caller's. Harnesses come from self-reported client names, and unrecognized or missing names read as Other.

get/user/mcp/harnesses

Request

  • Base URL
    https://api.traversal.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.traversal.com/user/mcp/harnesses
  • Auth
    none declared

Response

Successful Response

harnessesMcpHarness[] required

Each harness once, in McpHarness order. All time.

stream_cursorinteger nullable required

Highest seq on this user's harness stream. Null when nothing was published. Pass it as the stream_data cursor when opening the websocket. Each event carries the raw client_name; refetch this endpoint for harness labels.

Changes