# Pingoru status (remote · pingoru.io)

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

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `pingoru.io`: 36/100, [markdown](https://verifymcp.io/servers/io-pingoru-status/api-mcp.md), [page](https://verifymcp.io/servers/io-pingoru-status/api-mcp)
- remote · `pingoru.io`: 85/100 (this document), [markdown](https://verifymcp.io/servers/io-pingoru-status/api-mcp-public.md), [page](https://verifymcp.io/servers/io-pingoru-status/api-mcp-public)

## Channel facts

- Endpoint: `https://pingoru.io/api/mcp-public/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 926 tokens (~132/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pingoru status MCP server?

Pingoru status is a hosted endpoint at https://pingoru.io/api/mcp-public/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "io-pingoru-status": {
      "type": "http",
      "url": "https://pingoru.io/api/mcp-public/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-pingoru-status]
url = "https://pingoru.io/api/mcp-public/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-pingoru-status": {
      "type": "remote",
      "url": "https://pingoru.io/api/mcp-public/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-pingoru-status --url 'https://pingoru.io/api/mcp-public/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-pingoru-status:
    url: "https://pingoru.io/api/mcp-public/"
```

### Netclaw

```json
{
  "McpServers": {
    "io-pingoru-status": {
      "Transport": "http",
      "Url": "https://pingoru.io/api/mcp-public/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-pingoru-status -t streamable-http -u 'https://pingoru.io/api/mcp-public/'
```

### Other

```json
{
  "mcpServers": {
    "io-pingoru-status": {
      "type": "http",
      "url": "https://pingoru.io/api/mcp-public/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 85, +1)

- [security] Stability: 0.97 → pass
- [functional] Server version: 1.27.0 → 1.30.0

### 2026-11-18 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 81, +7)

- [security improvement] Authorization: unverified → partial
- [security] Tool “component_status” rewrote its description, which is the text the model reads
- [security] Tool “provider_components” rewrote its description, which is the text the model reads
- [security] Tool “provider_incidents” rewrote its description, which is the text the model reads
- [security] Tool “provider_status” rewrote its description, which is the text the model reads
- [security] Tool “search_providers” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 728 → 926
- [functional] New tool “alert_signup_link”
- [cosmetic] Tool “search_providers” changed its title: Find a service
- [cosmetic] Tool “component_status” changed its title: Check one component
- [cosmetic] Tool “incident_detail” changed its title: Read one incident
- [cosmetic] Tool “provider_components” changed its title: List a service's components
- [cosmetic] Tool “provider_incidents” changed its title: Recent incidents for a service
- [cosmetic] Tool “provider_status” changed its title: Check a service's status

### 2026-11-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 72, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (7)

### `provider_status` (~206 tokens)

Check a service's 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 the fuzzy fallback was used.

    The response has the service's Pingoru page (pingoru_url), the page
    where an email alert for it can be set up (alert_url, on the public
    endpoint, with a short note about it while an incident is open) and
    the vendor's own status page (status_url).

Input parameters:

- `slug` (string, required)

### `provider_components` (~101 tokens)

List a service's 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). The response has the service's Pingoru
    page (pingoru_url).

Input parameters:

- `only_problematic` (boolean)
- `slug` (string, required)

### `component_status` (~104 tokens)

Check one component

Pinpoint the status of one component by name (case-insensitive
    substring match). Returns an error listing the candidates when the
    name matches several components. The response has the service's
    Pingoru page (pingoru_url) and, when the component is in an open
    incident, that incident with its own page.
    Slug accepts shorthand / typos via fuzzy fallback.

Input parameters:

- `component` (string, required)
- `slug` (string, required)

### `provider_incidents` (~170 tokens)

Recent incidents for a service

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). The response's own pingoru_url is the
    service's outage history page. Pass component (substring match on
    component name) to scope to one component. Slug accepts shorthand /
    typos via fuzzy fallback.

Input parameters:

- `component`
- `days` (integer)
- `slug` (string, required)

### `incident_detail` (~121 tokens)

Read one incident

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.

Input parameters:

- `incident_id` (integer, required)
- `slug` (string, required)

### `search_providers` (~96 tokens)

Find a service

Find providers by name or slug. Use when the exact slug is not
    known ('look up that DBaaS… planetscale?'). Typos and shorthand
    still match: 'aws', 'gcp' and 'githb' all resolve to the right
    vendor. Each result has its Pingoru page (pingoru_url).

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `alert_signup_link` (~82 tokens)

Get a link to set up an alert

Returns the Pingoru page where the user can enter an email address
    to be told when this service's status changes. Use only when the
    user asks to be notified or alerted about a service. It does not
    create an alert itself. Slug accepts shorthand / typos via fuzzy
    fallback.

Input parameters:

- `slug` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-pingoru-status/api-mcp-public#diagnostics

## Score history

- 2026-11-21: 85
- 2026-11-20: 85
- 2026-11-19: 84
- 2026-11-18: 84
- 2026-11-17: 83
- 2026-11-16: 83
- 2026-11-15: 82
- 2026-11-14: 82
- 2026-11-13: 82
- 2026-11-12: 81
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 73
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 70
- 2026-10-31: 69
- 2026-10-30: 69
- 2026-10-29: 68
- 2026-10-28: 68
- 2026-10-27: 67
- 2026-10-26: 67
- 2026-10-25: 66
- 2026-10-24: 66
- 2026-10-23: 65

## Common questions

### What is the Pingoru status MCP server?

Pingoru status is an MCP server listed in the public MCP registry as io.pingoru/status. Live status, incidents and maintenance windows for 8,000+ cloud and SaaS status pages. This page covers its hosted endpoint (https://pingoru.io/api/mcp-public/).

### Is the Pingoru status MCP server safe to use?

Pingoru status scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Pingoru status MCP server expose?

Pingoru status exposes 7 tools: provider_status, provider_components, component_status, provider_incidents, incident_detail, and 2 more. Their descriptions and schemas cost roughly 880 tokens of context every time the server is loaded.

### Does the Pingoru status MCP server require authentication?

No. We connected to Pingoru status without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Pingoru status MCP server still maintained?

Pingoru status is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Pingoru status MCP server?

VerifyMCP ran 13 checks on Pingoru status, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pingoru.io/api/mcp-public/
- Website: https://pingoru.io/features/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-pingoru-status/api-mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-pingoru-status/api-mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-pingoru-status/api-mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/io-pingoru-status/api-mcp-public
