Skip to content
Error codes · Outages & the public API

RU-6004: Keyless MCP rate limited

Your address called the keyless MCP endpoint faster than its per-IP budget allows. This budget is deliberately tighter than the keyed one: a keyless call cannot be attributed to an account and, unlike the public outage JSON endpoint, an MCP response cannot be cached, so every call costs a fresh read.

Where it is raised

  • Keyless MCP endpoint, the per-address budget

What triggers it

The keyless endpoint allows 60 requests a minute per client address. A request carrying several tool calls spends one unit per extra call, so batching does not get around the limit, and a refusal can come before the body is read or after it is inspected.

Example response

POST https://mcp.realuptime.io/public
HTTP 429
retry-after: <seconds>

{
  "error": "Rate limit exceeded on the keyless MCP endpoint. Wait and retry, or use an API key for a larger per-key budget.",
  "code": "RU-6004",
  "docs": "https://realuptime.io/kb/errors/ru-6004",
  "retryAfterSeconds": "<seconds>"
}

Common causes

  • An agent polling an outage tool in a loop instead of asking once.
  • Many callers behind one shared egress address, which share a single per-IP budget.
  • Protocol overhead: one assistant question costs several requests (initialize, tools/list, then the tool call).

How to fix it

  1. Honor the Retry-After header before retrying.
  2. Ask once and reuse the answer: readings only change once per probe cycle (10 minutes).
  3. For sustained or shared-egress use, switch to the keyed MCP endpoint with an API key, which has its own larger per-key budget.
  4. For a single service reading, the cacheable JSON endpoint at /api/v1/outages/<slug> is cheaper than an MCP round trip.

Related codes