io.github.mrfentmen/statping-mcp
NPM · STATPING-MCP
Service rollup, ports, DNS propagation and TLS chains - no API key.
Available components
Last scanned (2 hours ago)
Scores higher than 44% 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 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
- 30 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 4 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
- Tool/resource definitions use about 765 tokens (~85/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +6
- Stability: unverified → 0.40 ▲ functional
- 2 Oct 26 65
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 23 Oct 2026 · Analysed npm/statping-mcp@1.0.2
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 | 30 |
| 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 →
cert_forecast Certificate forecast ~153
Judge a host's certificate by what it leaves you rather than by the chain alone: how many days of validity remain and how many the term has in total, the key size and curve, whether the subject alternative names actually cover the hostname you asked about, whether the chain is trusted, the handshake time, and what to do about a short term or a key under 2048 bits. The existing TLS chain tool reports the chain and trust but none of these.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to connect to, e.g. example.com. |
| port | integer | – | TLS port. Default 443. |
| warnDays | integer | – | Days of remaining validity that count as urgent. Default 30. |
No output schema declared.
No examples provided.
check_services Check services ~48
Up/down sweep of up to 10 services in one call, with status code and response time for each.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | Up to 10 service URLs to check in one call. |
No output schema declared.
No examples provided.
dns_propagation DNS propagation ~76
Ask Cloudflare, Google and AdGuard for the same record and report whether they agree, plus the lowest TTL.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to look up, for example example.com. |
| type | string | – | Record type: A, AAAA, NS, MX, TXT or CAA. Defaults to A. |
No output schema declared.
No examples provided.
dns_records DNS records ~122
Read the DNS record types the existing propagation tool never asks for: AAAA, MX, TXT, NS, CNAME, SOA and CAA alongside A. Every type is asked of two resolvers over DoH and compared, so a record still in flight shows as a disagreement between them rather than as a single answer. The existing DNS tool queries A records only.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. example.com. |
| types | string | – | Comma separated record types. Default A, AAAA, MX, TXT, NS. |
No output schema declared.
No examples provided.
header_audit Header audit ~129
Fetch a URL and report every response header it returned, with the security-relevant ones marked present or absent and what each one is for, so a missing HSTS or content security policy is visible. An optional path audits a different route on the same host, since headers are often set per route. The existing service_status reads only content-type, server and location out of every response it makes.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Extra path to audit on the same host, e.g. /api/health. |
| url | string | yes | URL or hostname, e.g. https://example.com. |
No output schema declared.
No examples provided.
port_check Port check ~72
Check whether TCP ports on a host accept connections, with the service usually found on each port.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname, for example db.example.com. |
| ports | array | – | Up to 10 TCP ports, for example [443, 5432]. Defaults to 443 and 80. |
No output schema declared.
No examples provided.
service_status Service status ~49
Detail for one service: HTTP status, response time, server, redirect chain and the first text on the page.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Service URL or hostname, for example https://example.com. |
No output schema declared.
No examples provided.
ssl_chain TLS chain ~49
The whole certificate chain from the live handshake: leaf, intermediates, expiry and whether the chain is trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname to read the chain from, for example example.com. |
No output schema declared.
No examples provided.
status_summary Status summary ~67
The rollup a status page shows: how many services are up, which are down, the slowest one and the overall state.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | Up to 10 service URLs to roll up, for example ['https://api.example.com', 'https://example.com']. |
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/statping-mcp server?
io.github.mrfentmen/statping-mcp runs locally as an npm package, launched with npx -y statping-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 · statping-mcp
claude mcp add mrfentmen-statping-mcp -- npx -y statping-mcp
What is the io.github.mrfentmen/statping-mcp server?
io.github.mrfentmen/statping-mcp is listed in the public MCP registry as io.github.mrfentmen/statping-mcp. Service rollup, ports, DNS propagation and TLS chains - no API key. This page covers its npm package (statping-mcp).
Is the io.github.mrfentmen/statping-mcp server safe to use?
io.github.mrfentmen/statping-mcp scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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.mrfentmen/statping-mcp server expose?
io.github.mrfentmen/statping-mcp exposes 9 tools: status_summary, check_services, service_status, port_check, dns_propagation, and 4 more. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/statping-mcp server still maintained?
io.github.mrfentmen/statping-mcp is still listed as active in the MCP registry. We last reached this channel on 23 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.mrfentmen/statping-mcp server under?
io.github.mrfentmen/statping-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.