MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

Pingoru status

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

Checks passed
11 / 22

3 failed · 8 not measured

Median response
942 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
6

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
220
Publisher identityCan the publisher be traced to its source?
312

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 942 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name pingoru-public.

  • Pass
    Lists tools

    tools/list returned 6 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 942 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 942 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    0 of 12 parameters have a description (0%). The bar is 80%.

  • Fail
    Safety hints

    6 tools set neither readOnlyHint nor destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-10-21T15:34:57.437114Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Pingoru status

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 6

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.

Discovered
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 May 3 outage'. Covers the last 30 days plus anything still open. Slug accepts shorthand / typos via fuzzy fallback.

Discovered
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).

Discovered
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), 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.

Discovered
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 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.

Discovered
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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected942 ms6