# Pingoru status Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Pingoru status

Check if cloud services and apps are down or having problems right now

- Record: https://musedirectory.ai/connector/pingoru-status
- Category: Research & Data
- Developer: Pingoru (https://pingoru.io/features/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1501ms, checked 2026-10-29T18:26:42Z
- Endpoint: https://pingoru.io/api/mcp-public/
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T18:26:42Z)
- Source: Found in the official MCP Registry (io.pingoru/status) https://registry.modelcontextprotocol.io/v0/servers?search=io.pingoru%2Fstatus

Checks live status pages for 8,000+ cloud and SaaS services including AWS, GitHub, Google Cloud and others. Shows current incidents, maintenance windows, affected components and incident history to help you understand service outages.

Example request: "Is GitHub down right now?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Pingoru status to help me. It is a free service with an MCP server at https://pingoru.io/api/mcp-public/. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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 se
- 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_progres
- 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 h
- 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. 

Screening checks:
- MCP handshake: pass (Answered in 1501ms)
- Domain against threat feeds (Cloudflare security DNS): pass (pingoru.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (6 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)