Test an MCP server connection
Connects to the MCP server, lists its tools, and disconnects — no persistence side effect. The practical way to confirm a URL/path and auth are correct before attaching the server to an agent. Strictly rate-limited: this makes a real outbound network call on every request. The result (pass/fail, tool count, timestamp) is persisted as an advisory status on the server — never a gate on attaching it to an agent, since a pass now doesn’t guarantee it’s still reachable later.
Authorizations
A long-lived, privileged API key (ek_... prefix), minted once from the dashboard. Intended for trusted server-side use only; never expose it in client-side code. Send as Authorization: Bearer ek_.... Required by every Calls, Batches, Agents, Tools, MCP Servers, Documents, and Realtime route.