Where it is raised
- Keyless MCP endpoint, tool names are checked first
What triggers it
The request names a tool in its JSON-RPC body that exists only on the keyed endpoint. The reply carries the offending tool name and the full list of the 4 tools the keyless endpoint serves. A call to an unknown tool name is not this code. A batch is inspected tool by tool, and the first keyed-only tool in it decides the refusal.
Example response
POST https://mcp.realuptime.io/public
HTTP 403
{
"error": "The keyless MCP endpoint serves read-only outage tools only. This tool reads or changes account data and needs an API key on the keyed endpoint.",
"code": "RU-1006",
"docs": "https://realuptime.io/kb/errors/ru-1006",
"tool": "list_checks",
"keylessTools": [
"is_service_down",
"get_regional_readings",
"get_report_volume",
"list_recent_incidents"
]
}Common causes
- An MCP client configured against the keyless endpoint tried an account tool such as list_checks or create_check.
- A client copied a tool name from the keyed API reference while pointed at the keyless URL.
How to fix it
- Generate an API key from your dashboard's API & MCP access section.
- Point the client at the keyed MCP endpoint with `Authorization: Bearer <api key>` and retry.
- To use the keyless endpoint, call only the outage tools it lists in tools/list.