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

Service rollup, ports, DNS propagation and TLS chains - no API key.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `statping-mcp`
- Version: `1.0.2`
- 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-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **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 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 765 tokens (~85/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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/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.

### Claude

```bash
claude mcp add mrfentmen-statping-mcp -- npx -y statping-mcp
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "mrfentmen-statping-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "statping-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-10-23 (score 75, +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.

### 2026-10-21 (score 74, +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-10-19 (score 73, +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-16 (score 72, +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-14 (score 71, +6)

- [functional improvement] Stability: unverified → 0.40

### 2026-10-02 (score 65)

First indexed and scored.

## MCP tools (9)

### `status_summary` (~67 tokens)

Status summary

The rollup a status page shows: how many services are up, which are down, the slowest one and the overall state.

Input parameters:

- `urls` (array, required): Up to 10 service URLs to roll up, for example ['https://api.example.com', 'https://example.com'].

### `check_services` (~48 tokens)

Check services

Up/down sweep of up to 10 services in one call, with status code and response time for each.

Input parameters:

- `urls` (array, required): Up to 10 service URLs to check in one call.

### `service_status` (~49 tokens)

Service status

Detail for one service: HTTP status, response time, server, redirect chain and the first text on the page.

Input parameters:

- `url` (string, required): Service URL or hostname, for example https://example.com.

### `port_check` (~72 tokens)

Port check

Check whether TCP ports on a host accept connections, with the service usually found on each port.

Input parameters:

- `host` (string, required): Hostname, for example db.example.com.
- `ports` (array): Up to 10 TCP ports, for example [443, 5432]. Defaults to 443 and 80.

### `dns_propagation` (~76 tokens)

DNS propagation

Ask Cloudflare, Google and AdGuard for the same record and report whether they agree, plus the lowest TTL.

Input parameters:

- `domain` (string, required): Domain to look up, for example example.com.
- `type` (string): Record type: A, AAAA, NS, MX, TXT or CAA. Defaults to A.

### `ssl_chain` (~49 tokens)

TLS chain

The whole certificate chain from the live handshake: leaf, intermediates, expiry and whether the chain is trusted.

Input parameters:

- `host` (string, required): Hostname to read the chain from, for example example.com.

### `header_audit` (~129 tokens)

Header audit

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.

Input parameters:

- `path` (string): Extra path to audit on the same host, e.g. /api/health.
- `url` (string, required): URL or hostname, e.g. https://example.com.

### `dns_records` (~122 tokens)

DNS records

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.

Input parameters:

- `domain` (string, required): Domain name, e.g. example.com.
- `types` (string): Comma separated record types. Default A, AAAA, MX, TXT, NS.

### `cert_forecast` (~153 tokens)

Certificate forecast

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.

Input parameters:

- `host` (string, required): 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.

## Diagnostics

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

## Score history

- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 65
- 2026-10-12: 65
- 2026-10-11: 65
- 2026-10-04: 65
- 2026-10-03: 65
- 2026-10-02: 65

## Common questions

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

## Links

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