ProbeOps

You can run the ProbeOps MCP Server locally to perform infrastructure diagnostics from multiple global regions. It executes tools like SSL checks, DNS lookups, latency measurements, and more, all from six regions simultaneously. You don’t need an API key for quick testing; you can run it with a single command and scale up with an API key for full access.

How to use

Use an MCP-compatible client to connect to the ProbeOps MCP Server. You will send tool requests through your MCP client, and the server will return per-region results along with a quota footer showing remaining usage. With a valid API key, you gain access to extra tools, more regions, and higher limits. Each diagnostic call runs from all configured regions so you can compare performance and availability globally.

How to install

Prerequisites: you need Node.js version 18.0.0 or newer installed on your machine. You may also opt to install Playwright later if you want screenshots for geo-browse results.

# Install Node.js from https://nodejs.org if you don’t have it

# Quick start (no API key): run the MCP server using npx
npx -y @probeops/mcp-server

# With an API key (full access): set the key and run
export PROBEOPS_API_KEY=your-api-key-here
npx -y @probeops/mcp-server

Additional notes

The server supports two main ways to run from MCP clients: a standard HTTP-based endpoint (if a URL is provided by the deployment) and a self-contained local runtime via npx. If you are deploying locally, you can use the provided command to start the MCP server. When you start in demo mode, you will see fewer tools and a smaller regional scope, but you can upgrade by supplying an API key.

Configuration and security

Environment variables you may set when running the MCP server include the API key and the API base URL. The API key enables full tool access, while the base URL can point to a staging or self-hosted instance if required.

Troubleshooting

If you encounter connectivity or quota issues, verify that your API key is set correctly and that you are using the correct MCP client configuration. Ensure you are running Node.js 18+ and that the MCP server process is active. For CI/CD usage, set the API key as an environment variable and invoke the MCP server from any MCP-compatible client.

Available tools

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 across multiple regions

latency_test

HTTP latency from multiple regions with min/avg/max results

traceroute

Network path tracing with per-hop latency using TCP, UDP, or ICMP

port_check

Port open/closed/filtered checks from multiple regions

ping

ICMP ping with packet loss and round-trip times

whois

Domain registration information such as registrar and dates

nmap_port_check

Check multiple ports using nmap (not a full scan)

tcp_ping

TCP-level latency to a specific port (useful when ICMP is blocked)

keyword_check

Check if a keyword exists on a web page across regions

websocket_check

WebSocket endpoint connectivity check

banner_grab

Service banner/version detection on a port

api_health

API endpoint health check including status, response time, and availability