Home › Other › Tracekit MCP gateway

Tracekit MCP gateway

MCP gateway you deploy: a Tracekit signer decides and signs each call; agents send each run's token.

Python Remote
★ 137 stars Last pushed 2026-10-18 License: MIT

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Remote (streamable-http)

https://{tracekit_gateway}/mcp

Claude Code:

claude mcp add --transport http tracekit https://{tracekit_gateway}/mcp --header "X-Tracekit-Run: <YOUR_VALUE>" --header "Authorization: <YOUR_VALUE>"

Or add to your MCP client config:

{
  "mcpServers": {
    "tracekit": {
      "url": "https://{tracekit_gateway}/mcp",
      "headers": {
        "X-Tracekit-Run": "<YOUR_VALUE>",
        "Authorization": "<YOUR_VALUE>"
      }
    }
  }
}
  • X-Tracekit-Run required secret — <run_id>.<run_token> of the agent's run (register_run): new for every run, so the agent framework sets it per run; one typed in once works for one run
  • Authorization secret — Bearer <token>: the agent's identity, when the gateway's http.authenticators accept a bearer or Kubernetes service account token (else a client certificate)

Related servers

Data from the Official MCP Registry