io.pingoru/status · v1.0.0 · cloud-and-infra
Pingoru status is healthy: it completed an MCP handshake in 1852 ms and exposes 6 tools.
Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages.
Endpoint: https://pingoru.io/api/mcp-public/ (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 6 |
| Latency | 1852 ms |
| Last checked (UTC) | 2026-10-21T16:36:00.903Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-21T16:36:00.903Z | Healthy | 1852 |
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?'. slug: Provider slug or human name. Exact slug ('github', 'amazon-web-services', 'google-cloud') is matched first; on miss we fall back to a searc |
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_problematic=true to filter out the operational ones. Slug accepts shorthand / typos via fuzzy fallback (see provider_status docstring). |
component_status | Pinpoint the status of one component by name (case-insensitive substring match). Returns an error when the name matches multiple components — the agent should ask the user to disambiguate. Slug accepts shorthand / typos via fuzzy fallback. |
provider_incidents | Recent incident history for a provider (days clamped to 1-30), plus a separate `maintenance` list: maintenance scheduled or held in the window, including upcoming windows. Each item has its current status (investigating / identified / monitoring / resolved, scheduled / in_progress / |
incident_detail | Full record for one incident or maintenance: current status, impact, start / resolve times and duration, scheduled window (for maintenance), affected components, the vendor's link, the Pingoru page (pingoru_url) and every status update with its timestamp. Use to summarise 'what happe |
search_providers | Find providers by name or slug. Use when the agent does not know the exact slug ('look up that DBaaS… planetscale?'). Uses Meilisearch under the hood so typos and shorthand still match — 'aws', 'gcp', 'githb', 'k8s' all resolve to the right vendor. |