# io.github.mrfentmen/statuspage-mcp (npm · statuspage-mcp)

Query Statuspage management API: pages, page details, incidents.

- Trust score: 64/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `statuspage-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp)

## Channel facts

- Registry: `npm`
- Package: `statuspage-mcp`
- Version: `1.1.0`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 13/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it.
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 301 tokens (~30/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 io.github.mrfentmen/statuspage-mcp server?

io.github.mrfentmen/statuspage-mcp runs locally as an npm package, launched with npx -y statuspage-mcp. 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 mrfentmen-statuspage-mcp -- npx -y statuspage-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-statuspage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "statuspage-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-statuspage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "statuspage-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-statuspage-mcp -- npx -y statuspage-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-statuspage-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "statuspage-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-statuspage-mcp --command npx --arg -y --arg statuspage-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-statuspage-mcp:
    command: "npx"
    args: ["-y", "statuspage-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-statuspage-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "statuspage-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-statuspage-mcp -t stdio -c npx -a -y statuspage-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-statuspage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "statuspage-mcp"
      ]
    }
  }
}
```

## 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-05 (score 64, +1)

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

### 2026-11-03 (score 63, +1)

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

### 2026-10-31 (score 62, +1)

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

### 2026-10-29 (score 61, +1)

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

### 2026-10-27 (score 60, +1)

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

### 2026-10-25 (score 59, +1)

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

### 2026-10-24 (score 58, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 63, +1)

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

## MCP tools (10)

### `list_pages` (~20 tokens)

List pages

Status pages the key can read, with id and name.

### `get_page` (~48 tokens)

Get page

One status page by id, with components and status.

Input parameters:

- `page_id` (string, required): Statuspage page ID, e.g. 1a2b3c4d5e6f

### `list_incidents` (~47 tokens)

List incidents

Recent incidents on a page, newest first.

Input parameters:

- `page_id` (string, required): Statuspage page ID, e.g. 1a2b3c4d5e6f

### `incident_details` (~31 tokens)

Incident details

Single incident.

Input parameters:

- `incident_id` (string, required): Incident ID.
- `page_id` (string, required): Page ID.

### `incident_updates` (~31 tokens)

Incident updates

Update timeline.

Input parameters:

- `incident_id` (string, required): Incident ID.
- `page_id` (string, required): Page ID.

### `components` (~20 tokens)

Components

Status components.

Input parameters:

- `page_id` (string, required): Page ID.

### `component_details` (~31 tokens)

Component details

Single component.

Input parameters:

- `component_id` (string, required): Component ID.
- `page_id` (string, required): Page ID.

### `subscribers` (~20 tokens)

Subscribers

Page subscribers.

Input parameters:

- `page_id` (string, required): Page ID.

### `upcoming_maintenance` (~22 tokens)

Upcoming maintenance

Scheduled windows.

Input parameters:

- `page_id` (string, required): Page ID.

### `maintenance_details` (~31 tokens)

Maintenance details

Single window.

Input parameters:

- `maintenance_id` (string, required): Maintenance ID.
- `page_id` (string, required): Page ID.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 62
- 2026-11-01: 62
- 2026-10-31: 62
- 2026-10-30: 61
- 2026-10-29: 61
- 2026-10-28: 60
- 2026-10-27: 60
- 2026-10-26: 59
- 2026-10-25: 59
- 2026-10-24: 58
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 60
- 2026-10-20: 60
- 2026-10-19: 60
- 2026-10-18: 60
- 2026-10-17: 45

## Common questions

### What is the io.github.mrfentmen/statuspage-mcp server?

io.github.mrfentmen/statuspage-mcp is listed in the public MCP registry as io.github.mrfentmen/statuspage-mcp. Query Statuspage management API: pages, page details, incidents. This page covers its npm package (statuspage-mcp).

### Is the io.github.mrfentmen/statuspage-mcp server safe to use?

io.github.mrfentmen/statuspage-mcp scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.mrfentmen/statuspage-mcp server expose?

io.github.mrfentmen/statuspage-mcp exposes 10 tools: list_pages, get_page, list_incidents, incident_details, incident_updates, and 5 more. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/statuspage-mcp server still maintained?

io.github.mrfentmen/statuspage-mcp 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 io.github.mrfentmen/statuspage-mcp server under?

io.github.mrfentmen/statuspage-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mrfentmen/statuspage-mcp server?

VerifyMCP ran 15 checks on io.github.mrfentmen/statuspage-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mrfentmen/statuspage-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/statuspage-mcp
- Socket report: https://socket.dev/npm/package/statuspage-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-statuspage-mcp/statuspage-mcp