Statuspage
NPM · @PIPEWORX/MCP-STATUSPAGE · 2 COMPONENTS
Service status / uptime MCP — Atlassian Statuspage v2.
Available components
Last scanned (6 hours ago)
Scores higher than 61% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-statuspage). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1020 tokens (~255/item across 4 items; 4 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-statuspage@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-statuspage |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-statuspage/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560312975 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c701f98e945d8f95d4c8bdbc53804ee0c08ec7c6c04ee267d50ce8042ee291f7badfde1ca9c78c3306a91f7c3bea59a184a8de13aab54494ea8077d93 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
statuspage_check ~320
Is a service down right now? Live service status, outage and uptime check for 190 vendors that publish an Atlassian Statuspage — OpenAI, Anthropic/Claude, GitHub, Cloudflare, Vercel, Netlify, DigitalOcean, MongoDB, Snowflake, Datadog, Twilio, SendGrid, Zoom, Discord, Shopify, Coinbase, Plaid, Figma, Dropbox, Atlassian/Jira and more. Returns the current status indicator (none / minor / major / critical / maintenance), the vendor's own status line such as "All Systems Operational" or "Partial System Outage", every component currently degraded or offline, open incidents with their latest update text and how long they have been running, and upcoming scheduled maintenance where the page publishes it. Use for questions about downtime, outages, service health, incidents in progress and whether an API or platform is working. Pass status_host to check any other vendor running a Statuspage.
| Name | Type | Req | Description |
|---|---|---|---|
| include_components | boolean | – | Include every component and its status, rather than only the degraded ones (default false). |
| status_host | string | – | Statuspage hostname to query directly, e.g. "status.somevendor.com". Use for any vendor outside the curated map. Overrides vendor when both are given. |
| vendor | string | – | Vendor name or key, forgiving about case and spacing: "openai", "OpenAI", "open ai", "github", "claude", "cloudflare". Call statuspage_list_vendors for the full covered set. |
No output schema declared.
No examples provided.
statuspage_incidents ~272
Incident and outage history for a vendor's status page — what broke, when, and whether it is fixed. Covers 190 verified Atlassian Statuspage vendors across AI providers, clouds, developer platforms, payments and communications. Each incident returns its title, lifecycle status (investigating / identified / monitoring / resolved), impact level (none / minor / major / critical), the time it started, the time it resolved, how long it lasted, the affected components, and the text of the latest update the vendor posted. Set unresolved_only to see only incidents that are still open. Use for outage history, past downtime, current incidents and postmortem timelines. Pass status_host for vendors outside the curated map.
| Name | Type | Req | Description |
|---|---|---|---|
| include_all_updates | boolean | – | Include the full update timeline for each incident rather than only the latest update (default false). |
| limit | number | – | Maximum incidents to return, 1-50 (default 10). |
| status_host | string | – | Statuspage hostname to query directly, e.g. "status.somevendor.com". Overrides vendor when both are given. |
| unresolved_only | boolean | – | Return only incidents that are still open (default false). |
| vendor | string | – | Vendor name or key, e.g. "cloudflare", "github", "anthropic". |
No output schema declared.
No examples provided.
statuspage_list_vendors ~208
Which companies this service-status pack can answer for: 190 verified Atlassian Statuspage hosts across AI and model providers, cloud and hosting, databases and observability, developer tools, payments and fintech, communications, and business SaaS. Returns the total count plus each vendor's lookup key, display name, category and status hostname, so a vendor name can be confirmed before calling statuspage_check instead of guessed. Also lists well-known companies whose status pages use a different format, together with the URL a human should open. Filter by category or search text.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to one category: ai, cloud, data, devtools, payments, comms, saas. |
| include_elsewhere | boolean | – | Also list known vendors that publish status in another format, with the URL to open (default false). |
| query | string | – | Substring filter over vendor key, display name and aliases, e.g. "cloud" or "git". |
No output schema declared.
No examples provided.
statuspage_multi_check ~168
Check the live service status of several vendors at once — "are any of my providers down right now?". Takes a list of vendor names or Statuspage hostnames and returns one compact row each: status indicator, the vendor's status line, open incident count and degraded component count, plus a roll-up naming which are operational, which are degraded or in an outage, and which could not be reached. Use for dependency health sweeps, incident triage across a stack, and monitoring a set of upstream APIs in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| vendors | array | yes | Vendor names/keys, or bare Statuspage hostnames (anything containing a dot is treated as a host). 1-20 entries, e.g. ["openai", "anthropic", "github", "cloudflare"]. |
No output schema declared.
No examples provided.
How do I install the Statuspage MCP server?
Statuspage runs locally as an npm package, launched with npx -y @pipeworx/mcp-statuspage. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-statuspage
claude mcp add pipeworx-io-statuspage -- npx -y @pipeworx/mcp-statuspage
What is the Statuspage MCP server?
Statuspage is an MCP server listed in the public MCP registry as io.github.pipeworx-io/statuspage. Service status / uptime MCP, Atlassian Statuspage v2. This page covers its npm package (@pipeworx/mcp-statuspage).
Is the Statuspage MCP server safe to use?
Statuspage scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Statuspage MCP server expose?
Statuspage exposes 4 tools: statuspage_check, statuspage_incidents, statuspage_list_vendors, statuspage_multi_check. Their descriptions and schemas cost roughly 968 tokens of context every time the server is loaded.
Is the Statuspage MCP server still maintained?
Statuspage is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Statuspage MCP server under?
Statuspage declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.