MCP

Send an MCP JSON-RPC message

The MCP Streamable HTTP transport endpoint. Accepts one JSON-RPC 2.0 message; a request (with id) returns its JSON-RPC response, and a notification (no id) returns 202 with no body. Protocol-level failures inside a well-formed request are reported as a 200 carrying a JSON-RPC error, per the JSON-RPC specification. Rate limits are described on the 429 response.

GET and DELETE answer 405 Method Not Allowed with Allow: POST: this server offers no server-initiated SSE stream and no session termination.

post/v1/mcp/messages

Request

  • Base URL
    https://statusstack.com/api
  • Auth
    • HTTP bearer
    • or API key in header X-API-Key

Request body

jsonrpc'2.0' required
methodstring required

Requests: initialize, ping, tools/list, tools/call, resources/list, resources/read; any other method with an id (including prompts/list — the server offers no prompts) answers JSON-RPC -32601. ping answers an empty result object, {}. Notifications (no id), such as notifications/initialized, are accepted whatever their method.

paramsobject

Example request

{
  "method": "tools/list"
}

Response

JSON-RPC response

OR

Changes

No recorded changes to this operation across all 1 revision of this API.