Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pingoru status

REMOTE · PINGORU.IO · 2 COMPONENTS

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

+3 this week 85 Trust /100

Last scanned (20 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1
    • Stability: 0.97 → pass security
    • Server version: 1.27.0 → 1.30.0 functional
  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 13 Nov 26 +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.

  • 12 Nov 26 +7
    • 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 security
    • Schema quality: 728 → 926 ▼ functional
    • New tool “alert_signup_link” functional
    • 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 cosmetic
  • 10 Nov 26 +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.

  • 8 Nov 26 +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.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://pingoru.io/api/mcp-public/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pingoru.io CN=YE2,O=Let's Encrypt,C=US 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA384 6116b6f969aa07917ee44ef892444bba55a
SANs: *.pingoru.io, pingoru.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of pingoru.io. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
pingoru.io. DS published 2371 13 Verified
pingoru.io. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pingoru.io/api/mcp-public/ Verified 200
http (plaintext) http://pingoru.io/api/mcp-public/ HTTPS enforced 301 https://pingoru.io/api/mcp-public/
MCP tools · 7 exposed · ~880 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
alert_signup_link ~82

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.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

component_status ~104

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.

NameTypeReqDescription
componentstringyes–
slugstringyes–

No output schema declared.

No examples provided.

incident_detail ~121

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.

NameTypeReqDescription
incident_idintegeryes–
slugstringyes–

No output schema declared.

No examples provided.

provider_components ~101

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

NameTypeReqDescription
only_problematicboolean––
slugstringyes–

No output schema declared.

No examples provided.

provider_incidents ~170

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.

NameTypeReqDescription
component–––
daysinteger––
slugstringyes–

No output schema declared.

No examples provided.

provider_status ~206

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

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

search_providers ~96

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

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

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.

remote · pingoru.io

# add to Claude Code
claude mcp add --transport http io-pingoru-status 'https://pingoru.io/api/mcp-public/'
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.