Probeops Mcp Server
Run SSL, DNS, latency, and traceroute checks from six global regions through your agent when debugging production or pre-release endpoints.
Overview
io.github.kumarprobeops/probeops-mcp-server is a MCP server for the Operate phase that runs multi-region SSL, DNS, ping, traceroute, port scan, and latency diagnostics for AI assistants.
What is this MCP server?
- Network diagnostics from 6 global regions via @probeops/mcp-server npx stdio
- Tools cover SSL, DNS, ping, whois, traceroute, port scan, and latency
- Optional PROBEOPS_API_KEY; demo mode available without a key per manifest
- Version 1.2.3 npm package with website probeops.com for fuller product context
- Lets agents reproduce user-geo failures without opening five terminal utilities
- Diagnostics from 6 global regions per server description
- npm package @probeops/mcp-server version 1.2.3
- Seven diagnostic capability areas: SSL, DNS, ping, whois, traceroute, port scan, latency
What problem does it solve?
When something fails only in certain countries, flipping between dig, openssl, and traceroute manually slows solo operators during an outage.
Who is it for?
Indie devs operating APIs or small SaaS who need quick external network truth from the agent during incidents or pre-launch checks.
Skip if: Teams needing deep application profiling, log aggregation, or internal Kubernetes metrics only in-cluster tools provide.
What do I get? / Deliverables
After you add the npx stdio server, your agent can run ProbeOps checks from six regions and return structured diagnostic context in one thread.
- Agent-triggered SSL, DNS, ping, whois, traceroute, port scan, and latency results
- Multi-region perspective on reachability and certificate health
- Faster incident triage without manual CLI hopping
Recommended MCP Servers
Journey fit
Production health and external vantage-point checks belong in Operate, where builders diagnose live systems. Monitoring is the canonical shelf because ProbeOps aggregates recurring external probes rather than authoring tests or deploying infra.
How it compares
External network probe MCP from six regions, not an in-repo test runner or cloud vendor native monitoring console.
Common Questions / FAQ
Who is probeops-mcp-server for?
Solo builders and tiny teams who operate internet-facing services and want Claude Code or Cursor to run ProbeOps network diagnostics on demand.
When should I use probeops-mcp-server?
Use it during Operate incidents or Ship hardening when you need SSL, DNS, latency, or routing checks from multiple global vantage points.
How do I add probeops-mcp-server to my agent?
Configure stdio with npx @probeops/mcp-server, set PROBEOPS_API_KEY if you have one, and register the server in your MCP client settings.