Statping Mcp

io.github.mrfentmenv1.0.2Updated Oct 2, 2026

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

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

Lets an assistant check service status rollups, ports, DNS propagation, and TLS certificate chains without an API key.

What it does
Statping Mcp is a local stdio MCP server that exposes checks around service availability and network configuration. Based on its description, it can produce a service rollup, inspect ports, trace DNS propagation, and walk TLS certificate chains. No tool list is published, so the exact tool names and parameters are not documented here.
When to use it
Worth adding when an assistant needs to verify whether a service is reachable, whether a port is open, whether DNS changes have propagated, or how a TLS chain is composed. Useful for quick operational triage during development or incident investigation.
Requirements
Runs as a local process on the user's machine, installed from the npm package statping-mcp over stdio. Desktop only; no web executable. The manifest declares no authentication, environment variables, or headers, and the description states no API key is needed. Network access is implied by DNS, port, and TLS checks.
Before you install
The server performs outbound network checks against hosts you point it at, so target names and addresses leave your machine. No credentials are requested by the manifest, but confirm the package source before installing since it runs locally with your user's network access.

Installation

In SourceWeft

  1. Open Statping Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.2LatestOct 2, 2026