KitScout

Categories › Cloud & DevOps › Monitoring, logs & incidents

Pingoru status

MCP serverVerified domain · pingoru.ioRemote● LiveFree to try

Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.

Install

Remote server: your requests and data go to pingoru.io. Claude Code: claude mcp add --transport http pingoru-status https://pingoru.io/api/mcp-public/ · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • provider_status — Get the current status and any active incidents for a status-page vendor. Use when the user asks 'is X down?' or 'is X having problems?'. sl
  • provider_components — List a provider's components with current status. Use to drill into 'which AWS components are broken right now?' style questions. Set only_p
  • component_status — Pinpoint the status of one component by name (case-insensitive substring match). Returns an error listing the candidates when the name match
  • provider_incidents — Recent incident history for a provider (days clamped to 1-30), plus a separate `maintenance` list: maintenance scheduled or held in the wind
  • incident_detail — Full record for one incident or maintenance: current status, impact, start / resolve times and duration, scheduled window (for maintenance),
  • search_providers — Find providers by name or slug. Use when the exact slug is not known ('look up that DBaaS… planetscale?'). Typos and shorthand still match:
  • alert_signup_link — Returns the Pingoru page where the user can enter an email address to be told when this service's status changes. Use only when the user ask

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools