Probeops MCP Server

MCP server for multi-region infrastructure diagnostics — SSL, DNS, ping, whois, traceroute, port check, latency, and geo-proxy browsing from 6 global

Remote serverstreamable-http

What is the Probeops MCP server?

Connect Probeops to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for multi-region infrastructure diagnostics — SSL, DNS, ping, whois, traceroute, port check, latency, and geo-proxy browsing from 6 global regions. The probeops mcp server is what makes that connection.

What the server does

MCP server for running infrastructure diagnostics from 6 global regions. SSL checks, DNS lookups, ping, whois, port checks, traceroute, latency tests, and more — each executed simultaneously from US East, US West, EU Central, Canada, India, and Australia.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • ssl_check — SSL/TLS certificate validity, expiry, issuer, TLS version, SANs, cross-region consistency
  • dns_lookup — DNS record lookup (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, PTR) with multi-region propagation check
  • is_it_down — Website up/down/partial status from multiple regions
  • latency_test — HTTP latency (TTFB) from multiple regions, returns min/avg/max
  • traceroute — Network path tracing with per-hop latency. TCP, UDP, or ICMP
  • port_check — Port open/closed/filtered check from multiple regions
  • ping — ICMP ping with packet loss and round-trip times
  • whois — Domain registration info: registrar, dates, nameservers
  • nmap_port_check — Check multiple ports open/closed using nmap (not a full scan)
  • tcp_ping — TCP-level latency to a specific port (works when ICMP is blocked)
  • keyword_check — Check if a keyword exists on a web page from multiple regions
  • websocket_check — WebSocket endpoint connectivity check

Credentials and setup notes

Configuration is passed through the environment: PROBEOPS_API_KEY, PROBEOPS_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js >= 18.0.0 - Playwright (optional) - only needed for geo_browse screenshots Without Playwright, geo_browse falls back to HTTP fetch (raw HTML, no screenshots).

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Probeops.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Probeops's toolset — ssl_check, dns_lookup, is_it_down and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kumarprobeops; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
ssl_checkSSL/TLS certificate validity, expiry, issuer, TLS version, SANs, cross-region consistency
dns_lookupDNS record lookup (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, PTR) with multi-region propagation check
is_it_downWebsite up/down/partial status from multiple regions
latency_testHTTP latency (TTFB) from multiple regions, returns min/avg/max
tracerouteNetwork path tracing with per-hop latency. TCP, UDP, or ICMP
port_checkPort open/closed/filtered check from multiple regions
pingICMP ping with packet loss and round-trip times
whoisDomain registration info: registrar, dates, nameservers
nmap_port_checkCheck multiple ports open/closed using nmap (not a full scan)
tcp_pingTCP-level latency to a specific port (works when ICMP is blocked)
keyword_checkCheck if a keyword exists on a web page from multiple regions
websocket_checkWebSocket endpoint connectivity check
banner_grabService banner/version detection on a port
api_healthAPI endpoint health check (HTTP status, response time, availability)

How to install the Probeops MCP server

{
  "mcpServers": {
    "probeops": {
      "command": "npx",
      "args": ["-y", "@probeops/mcp-server"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js >= 18.0.0 - Playwright (optional) - only needed for geo_browse screenshots Without Playwright, geo_browse falls back to HTTP fetch (raw HTML, no screenshots).
VariableDescriptionRequired
PROBEOPS_API_KEYCredential the server authenticates with.Yes
PROBEOPS_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Probeops to ssl check.
  • Use Probeops to dns lookup.
  • Use Probeops to is it down.

Frequently asked questions

It connects Probeops to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (ssl_check, dns_lookup, is_it_down, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Probeops directly.