Globalping
Run worldwide ping, traceroute, and DNS checks from your agent when users report flaky reachability or DNS mistakes.
Overview
com.mcparmory/globalping is an Operate-phase MCP server that runs global ping, traceroute, and DNS network tests from your agent.
What is this MCP server?
- Execute ping, traceroute, and DNS tests from distributed global probes
- Compare latency and resolution from multiple regions in one agent thread
- stdio MCP 1.0.3 via uvx mcparmory-globalping or Docker ghcr.io/mcparmory/globalping:1.0.3
- Supports ship perf sanity checks and operate incident triage alike
- Network diagnostic MCP—not application APM or log aggregation
- Server version 1.0.3
- 2 install packages (PyPI mcparmory-globalping and OCI ghcr.io/mcparmory/globalping:1.0.3)
- stdio transport; supports ping, traceroute, and DNS test types per server description
Community signal: 25 GitHub stars.
What problem does it solve?
You cannot reproduce user-reported network or DNS issues when diagnostics only run from your local machine.
Who is it for?
Indie operators debugging CDN, DNS, or regional outages with quick agent-triggered global network tests.
Skip if: Teams needing deep in-app tracing, RUM, or private corporate network probe fleets.
What do I get? / Deliverables
Your agent returns multi-region probe results so you can confirm routing, latency, or DNS propagation before and during incidents.
- Probe-backed ping, traceroute, and DNS results your agent can cite in postmortems
- Faster isolation of DNS vs routing issues during support and operate workflows
Recommended MCP Servers
Journey fit
After launch, solo operators debug production and support tickets where network path and DNS evidence matter—operate is the home for live diagnostic tooling. Monitoring fits because GlobalPing-style probes are observability for connectivity and resolution, not feature coding or marketing distribution.
How it compares
Global edge network probes via MCP, not a host metrics exporter or error-tracking SDK.
Common Questions / FAQ
Who is com.mcparmory/globalping for?
Solo founders and small teams running live APIs or sites who need the agent to run external ping, traceroute, and DNS checks from many locations.
When should I use com.mcparmory/globalping?
Use it in operate (and late ship perf checks) when investigating connectivity, DNS records, or latency complaints from real global vantage points.
How do I add com.mcparmory/globalping to my agent?
Add stdio MCP using uvx mcparmory-globalping 1.0.3 or ghcr.io/mcparmory/globalping:1.0.3, configure any GlobalPing API requirements from mcparmory docs, and enable the server in your MCP client.