Post-save health check on a registered server
Run a health check on an already-registered MCP server using its STORED (decrypted) credential, persist the verdict into the reserved metadata.health key, and re-pin the tool-definition hashes (rug-pull defense): a tool whose definition no longer matches its prior pinned hash is flagged as drifted and re-queued for operator approval. The health pill the dashboard renders reads metadata.health. 404 when the id is unknown to this agent. 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 Response
The health verdict — status, tool_count, checked_at, plus the drifted-tool list — in the standard { data, meta } envelope.