Skip to content

Pingoru status

by pingoru.io · remote · no sign-in to list tools · v1.0.0 · published by io.pingoru

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

Changes · 2
CompareRegistry entry

6 tools: 2 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Changes things 2Claude Code: ask
  • incident_detailFull record for one incident or maintenance: current status, impact, start / resolve times and duration, scheduled window (for maintenance), affected components, the vendor's link,…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 May 3 outage'. Covers the last 30 days plus anything still open. Slug accepts shorthand / typos via fuzzy fallback.
  • provider_incidentsRecent 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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), start and resolve times, duration, impact, affected components, the vendor's link and the Pingoru page (pingoru_url). Pass component (substring match on component name) to scope to one component. Slug accepts shorthand / typos via fuzzy fallback.
Only reads 4Claude Code: allow
  • component_statusPinpoint the status of one component by name (case-insensitive substring match).No findings

    Why it is in this group

    • The name "component_status" says "status": a word for reading.
    Description, as the server wrote it
    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_componentsList a provider's components with current status.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    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).
  • provider_statusGet the current status and any active incidents for a status-page vendor.No findings

    Why it is in this group

    • The name "provider_status" says "status": a word for reading.
    Description, as the server wrote it
    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 common shorthands ('aws', 'gcp', 'github actions') and minor typos still resolve. The response includes `matched_via: 'fuzzy'` and the original query when fuzzy fallback was used so the agent can confirm with the user.
  • search_providersFind providers by name or slug.No findings

    Why it is in this group

    • The name "search_providers" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__status__provider_status",
      "mcp__status__provider_components",
      "mcp__status__component_status",
      "mcp__status__search_providers"
    ],
    "ask": [
      "mcp__status__provider_incidents",
      "mcp__status__incident_detail"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as status. Review it before you use it.