io.github.Churman1113/pingcheck-mcp

NPM · PINGCHECK-MCP · SCANNED AUG 3

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

Available components

+43 this week 64 64 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency19

Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 5 days ago).Pass
Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified

Schema Quality & AI Usability73

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · pingcheck-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

{
  "mcpServers": {
    "churman1113-pingcheck-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "pingcheck-mcp"
      ]
    }
  }
}

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.

3 Aug 26 +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.
2 Aug 26 +63
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
1 Aug 26 −21
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
27 Jul 26 21

First indexed and scored.

Show 2 earlier entries Hide earlier entries

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 8 exposed · ~1,055 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.

Tool Tokens

pingcheck_check_now ~117

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 Output Examples

Name	Type	Req	Description
componentId	string	yes	The component id (from pingcheck_page_detail components list).

No output schema declared.

No examples provided.

pingcheck_create_component ~198

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 Output Examples

Name	Type	Req	Description
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	yes	Component display name, e.g. "API Gateway".
statusPageId	string	yes	The status page id (from pingcheck_list_my_pages).
url	string	yes	Target URL (e.g. https://api.example.com or db.example.com:5432).

No output schema declared.

No examples provided.

pingcheck_create_incident ~172

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 Output Examples

Name	Type	Req	Description
description	string	—	Detailed description of the issue.
impact	string	—	Impact level (default "minor").
status	string	—	Initial incident status (default "investigating").
statusPageId	string	yes	The status page id where the incident should appear (from pingcheck_list_my_pages).
title	string	yes	Incident title, e.g. "API returning 503 errors".

No output schema declared.

No examples provided.

pingcheck_delete_component ~76

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 Output Examples

Name	Type	Req	Description
componentId	string	yes	The component id to delete.

No output schema declared.

No examples provided.

pingcheck_list_my_pages ~98

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pingcheck_page_detail ~114

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 Output Examples

Name	Type	Req	Description
pageId	string	yes	The status page id returned by pingcheck_list_my_pages.

No output schema declared.

No examples provided.

pingcheck_public_status ~148

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 Output Examples

Name	Type	Req	Description
slug	string	yes	The status page slug, taken from the URL path after /status/. e.g. for https://pingcheck.cloud/status/acme the slug is "acme".

No output schema declared.

No examples provided.

pingcheck_update_incident ~132

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 Output Examples

Name	Type	Req	Description
incidentId	string	yes	The incident id to update.
message	string	yes	Update message visible to subscribers, e.g. "Root cause identified, deploying fix."
status	string	yes	New status for this update.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug