All servers · Monitoring & logs · Cloud & networking

Pingoru status

io.pingoru/status · v1.0.0

New (7 days)

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	experimental, prompts, resources, tools
Tool definitions	6 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

Description written by the publisher, not verified

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

Connect

streamable-http · https://pingoru.io/api/mcp-public/

claude mcp add --transport http status https://pingoru.io/api/mcp-public/

{
  "mcpServers": {
    "status": {
      "url": "https://pingoru.io/api/mcp-public/"
    }
  }
}

streamable-http · https://pingoru.io/api/mcp/

claude mcp add --transport http status https://pingoru.io/api/mcp/

{
  "mcpServers": {
    "status": {
      "url": "https://pingoru.io/api/mcp/"
    }
  }
}

Tools as reported by the server

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 search lookup so commo
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 / completed), star
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 happened during the M
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.

Website · JSON · Text for agents · Registry updated 2026-10-21