# io.github.Churman1113/pingcheck-mcp (npm · pingcheck-mcp)

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `pingcheck-mcp`
- Version: `0.2.1`
- 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/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).
  - Actively maintained (last published 5 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1055 tokens (~131/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add churman1113-pingcheck-mcp -- npx -y pingcheck-mcp
```

### Codex

```bash
codex mcp add churman1113-pingcheck-mcp -- npx -y pingcheck-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add churman1113-pingcheck-mcp --command npx --arg -y --arg pingcheck-mcp
```

### Hermes

```yaml
mcp_servers:
  churman1113-pingcheck-mcp:
    command: "npx"
    args: ["-y", "pingcheck-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "churman1113-pingcheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pingcheck-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-08-03 (score 64, +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-08-02 (score 63, +63)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-08-01 (score 0, −21)

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

### 2026-07-27 (score 21)

First indexed and scored.

## MCP tools (8)

### `pingcheck_public_status` (~148 tokens)

Read the live status of any PUBLIC PingCheck status page by its slug. No API key needed — status data is public. Returns overall status, each component (name, status, uptime %, response time, last checked), and active/resolved incidents. Use this when a user asks "is <service> up?" and you know its PingCheck slug, or after they paste a pingcheck.cloud status page URL. Example slug from https://pingcheck.cloud/status/my-api is "my-api".

Input parameters:

- `slug` (string, required): The status page slug, taken from the URL path after /status/. e.g. for https://pingcheck.cloud/status/acme the slug is "acme".

### `pingcheck_list_my_pages` (~98 tokens)

List all status pages YOU own on PingCheck. Requires PINGCHECK_API_KEY (your pk_... API key). Returns each page id, name, slug, public/private flag and overall status. Use this first when a user wants to check their own monitors but does not know the slug. (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

### `pingcheck_page_detail` (~114 tokens)

Get full detail for ONE of your own PingCheck status pages by its id (obtain ids from pingcheck_list_my_pages). Requires PINGCHECK_API_KEY. Returns components with uptime/response time and incident history. Use when the user wants a deep dive on a specific monitor. (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

Input parameters:

- `pageId` (string, required): The status page id returned by pingcheck_list_my_pages.

### `pingcheck_check_now` (~117 tokens)

Re-run monitoring for a specific component right now (on-demand check). Requires PINGCHECK_API_KEY. Pass the component id. Returns the fresh result (status, response time). Use when a user suspects a page is stale and wants a live re-check rather than waiting for the next cron tick. (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

Input parameters:

- `componentId` (string, required): The component id (from pingcheck_page_detail components list).

### `pingcheck_create_component` (~198 tokens)

Create a new monitoring component on one of YOUR PingCheck status pages. Requires PINGCHECK_API_KEY. Provide the status page id, component name, and target URL. A monitoring check runs immediately after creation. (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

Input parameters:

- `checkInterval` (number): Check interval in minutes (default 5).
- `description` (string): Short description of this component.
- `expectedStatus` (number): Expected HTTP status code (default 200).
- `method` (string): HTTP method (default GET).
- `name` (string, required): Component display name, e.g. "API Gateway".
- `statusPageId` (string, required): The status page id (from pingcheck_list_my_pages).
- `url` (string, required): Target URL (e.g. https://api.example.com or db.example.com:5432).

### `pingcheck_delete_component` (~76 tokens)

Delete a monitoring component from YOUR PingCheck status page by its id. Requires PINGCHECK_API_KEY. This is irreversible. (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

Input parameters:

- `componentId` (string, required): The component id to delete.

### `pingcheck_create_incident` (~172 tokens)

Create a new incident on one of YOUR PingCheck status pages. Requires PINGCHECK_API_KEY. Use this to report an outage, maintenance, or degradation. AI agents can create incidents automatically when monitoring detects failures — no manual login needed. (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

Input parameters:

- `description` (string): Detailed description of the issue.
- `impact` (string): Impact level (default "minor").
- `status` (string): Initial incident status (default "investigating").
- `statusPageId` (string, required): The status page id where the incident should appear (from pingcheck_list_my_pages).
- `title` (string, required): Incident title, e.g. "API returning 503 errors".

### `pingcheck_update_incident` (~132 tokens)

Update an existing incident on YOUR PingCheck status page — post a status update or resolve it. Requires PINGCHECK_API_KEY. Each call adds a new timeline entry. To close an incident, set status to "resolved". (Note: no PINGCHECK_API_KEY set — only public status pages are readable. Set the env var to read your own monitors.)

Input parameters:

- `incidentId` (string, required): The incident id to update.
- `message` (string, required): Update message visible to subscribers, e.g. "Root cause identified, deploying fix."
- `status` (string, required): New status for this update.

## Diagnostics

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

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 0
- 2026-07-31: 21
- 2026-07-30: 21
- 2026-07-28: 21
- 2026-07-27: 21

## Links

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