Test MCP Server Connectivity

Tests connectivity to an MCP server by spawning it (inside a sandbox), running session.initialize(), and returning the server’s reported name / version / description and connection latency.

The target server is identified by the X-Enkrypt-MCP-Registry-Server header — the gateway fetches its config from GET /mcp-registry/get-server using your apikey and uses the cloud’s 200/401/403 response as the authentication gate. No request body is required.

POST /mcp-playground/test-server

Test MCP Server Connectivity

cURL

curl --request POST \
  --url https://mcp.enkryptai.com/mcp-playground/test-server \
  --header 'X-Enkrypt-MCP-Registry-Server: <x-enkrypt-mcp-registry-server>' \
  --header 'apikey: <api-key>'

200

{
  "success": true,
  "message": "<string>",
  "error": "<string>",
  "data": {
    "saved_name": "<string>",
    "server_version": "<string>",
    "tool_count": 123,
    "tested_at": "2023-11-07T05:31:56Z"
  }
}

Authorizations

apikey · string · header · required

Headers

X-Enkrypt-MCP-Registry-Server · string · required

Registry server saved_name

Maximum string length: 32

Example:

"my-filesystem-server"

X-Enkrypt-MCP-Registry-Server-Version · string · default: v1

Registry server version (defaults to "v1")

Example:

"v1"

Response

200

application/json

Server test result

success · boolean

Whether the test was successful

message · string

Human-readable message about the test result

error · string | null

Error details if the test failed

data · object

Show child attributes