Pre-save connectivity probe for a candidate server
Test a candidate MCP server URL BEFORE saving it — SSRF-check the URL, resolve the supplied credential (static token verbatim, OAuth2 grant exchanged), and issue a JSON-RPC tools/list exactly as the agent_runtime would at discovery, so a green probe predicts the runtime will register it. Never persists a row; the verdict lists each discovered tool by name and strips the internal tool_definitions used by the post-save /test route. Owner/admin/developer role.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Response
The probe verdict — status (ok / auth_failed / unreachable), tool_count, per-tool names, checked_at — in the standard { data, meta } envelope.