# statping-mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.2
- **Author:** io.github.mrfentmen
- **License:** MIT
- **npm:** statping-mcp
- **Source:** https://github.com/mrfentmen/premium-mcps
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 9 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-03T17:14:21.546Z
- **Version scanned:** 1.0.2
- **CVEs:** none found by OSV at scan time

## Tools

9 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `status_summary` — The rollup a status page shows: how many services are up, which are down, the slowest one and the overall state.
- `check_services` — Up/down sweep of up to 10 services in one call, with status code and response time for each.
- `service_status` — Detail for one service: HTTP status, response time, server, redirect chain and the first text on the page.
- `port_check` — Check whether TCP ports on a host accept connections, with the service usually found on each port.
- `dns_propagation` — Ask Cloudflare, Google and AdGuard for the same record and report whether they agree, plus the lowest TTL.
- `ssl_chain` — The whole certificate chain from the live handshake: leaf, intermediates, expiry and whether the chain is trusted.
- `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 o
- `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 
- `cert_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 si

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"statping\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"statping-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/statping-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/statping-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/statping-mcp
- HTML page: https://forgeregistry.com/registry/statping-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.