Statping MCP server

Read from the package source without running it. The installed server may list more.

• 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 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 repor

• check_services

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

• dns_propagation

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

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

• 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

• port_check

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

• service_status

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

• ssl_chain

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

• status_summary

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

• Code scan9 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Safety score

65/100

higher than 20% of 48,255 servers

Tools

9

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

395

more than 85% of 12,191 servers with a package

Statping: common questions

Is Statping MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the Statping safety report

How do I install Statping?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Statping need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Statping maintained?

The latest release is v1.0.2.

How does Statping compare with other MCP servers?

safety score 65/100 (higher than 20% of 48,255 servers); tools 9 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.