Skip to main content
MCP Trail MCP Trail

Connection details & docsDocs

Summary of how end users connect through Guardian. Replace or extend with your canonical documentation when it is published.

This page is a marketing-site summary. Verify URLs, headers, and rotation steps against the live dashboard and product documentation.

What you share with assistant users

  • Guardian base URL — the stable proxy endpoint for the registered server (path/slug must match what clients call).
  • Access key — per-server bearer token; scoped to that Guardian server.
  • Transport hints — remote HTTP / gateway-style MCP clients typically use JSON-RPC over HTTPS to Guardian, not the raw upstream.

Rotation

If a key leaks, rotate or revoke it from the dashboard. Upstream MCP configuration does not need to change for clients that already target Guardian.

Where to go next

  • Features — policies, DLP, HITL, audit, and abuse controls.
  • Contact — demos, security reviews, and rollout questions.
  • Free MCP Playground — test your MCP endpoint through Guardian with a free MCP session risk calculator, free MCP traffic monitor, and free session logs.
  • Open the app — sign in for live connection details.