io.github.Churman1113/pingcheck-mcp
NPM · PINGCHECK-MCP · SCANNED OCT 4
PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.
Available components
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 Security98
- 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
- 31 of 93 dependencies flagged as unhealthy. 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 67 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- 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 Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
How do I install the io.github.Churman1113/pingcheck-mcp server?
io.github.Churman1113/pingcheck-mcp runs locally as an npm package, launched with npx -y pingcheck-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · pingcheck-mcp
claude mcp add churman1113-pingcheck-mcp -- npx -y pingcheck-mcp
{
"mcpServers": {
"churman1113-pingcheck-mcp": {
"command": "npx",
"args": [
"-y",
"pingcheck-mcp"
]
}
}
} {
"servers": {
"churman1113-pingcheck-mcp": {
"command": "npx",
"args": [
"-y",
"pingcheck-mcp"
]
}
}
} codex mcp add churman1113-pingcheck-mcp -- npx -y pingcheck-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"churman1113-pingcheck-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"pingcheck-mcp"
],
"enabled": true
}
}
} openclaw mcp add churman1113-pingcheck-mcp --command npx --arg -y --arg pingcheck-mcp
mcp_servers:
churman1113-pingcheck-mcp:
command: "npx"
args: ["-y", "pingcheck-mcp"] {
"McpServers": {
"churman1113-pingcheck-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"pingcheck-mcp"
]
}
}
} assistant mcp add churman1113-pingcheck-mcp -t stdio -c npx -a -y pingcheck-mcp
{
"mcpServers": {
"churman1113-pingcheck-mcp": {
"command": "npx",
"args": [
"-y",
"pingcheck-mcp"
]
}
}
} 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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 −3
- Stability: pass → 0.80 functional
- 30 Sept 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 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
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 4 Oct 2026 · Analysed npm/pingcheck-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
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.)
| 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.)
| 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.)
| 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.)
| 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 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.)
| 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".
| 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.)
| 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.
What is the io.github.Churman1113/pingcheck-mcp server?
io.github.Churman1113/pingcheck-mcp is listed in the public MCP registry as io.github.Churman1113/pingcheck-mcp. PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key. This page covers its npm package (pingcheck-mcp).
Is the io.github.Churman1113/pingcheck-mcp server safe to use?
io.github.Churman1113/pingcheck-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 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.Churman1113/pingcheck-mcp server expose?
io.github.Churman1113/pingcheck-mcp exposes 8 tools: pingcheck_public_status, pingcheck_list_my_pages, pingcheck_page_detail, pingcheck_check_now, pingcheck_create_component, and 3 more. Their descriptions and schemas cost roughly 1,055 tokens of context every time the server is loaded.
Is the io.github.Churman1113/pingcheck-mcp server still maintained?
io.github.Churman1113/pingcheck-mcp is still listed as active in the MCP registry. We last reached this channel on 4 October 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.Churman1113/pingcheck-mcp server under?
io.github.Churman1113/pingcheck-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.