Ping server

Loading server catalog…. Download catalog

POSThttps://app.advarde.com/mcp

Protocol

Available subject to your connection’s permissions.

Description: Check that the authenticated MCP server can respond.

Method: ping

Output: See the protocol description and workflow notes below.

Access: Workspace-scoped MCP authentication.

Authentication

Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.

For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.

Send these fields inside params. The JSON-RPC envelope is shown in the request example.

No additional properties are accepted.

Full JSON Schema

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}

200Successful protocol response

Inspect result.isError for tool-level failures, even when the HTTP status is 200.

202Notification accepted

MCP notifications return no JSON-RPC response body.

400Invalid request

Check the JSON-RPC envelope, parameters, and protocol version.

406Not acceptable

Accept must include application/json and text/event-stream.

429Rate limited

Wait for the Retry-After interval before making another request.

401Unauthorized

A valid, unexpired MCP bearer token is required.

403Access denied

Your connection needs access to this workspace and the requested operation.