
Probeops Mcp Server
io.github.kumarprobeopsPublished by GitHub account kumarprobeopsv1.2.3Updated Oct 24, 2026
Network diagnostics from 6 global regions. SSL, DNS, ping, whois, traceroute, port scan, latency.
Overview
Runs network and infrastructure diagnostics — SSL, DNS, ping, traceroute, port and latency checks — from up to six global regions.
- What you can do
- Check certificates, DNS records and domain registration (SSL check, DNS lookup with MX/TXT/NS/CNAME/CAA/PTR shortcuts, whois)
- Test reachability and performance (up/down status, ping, TCP ping, latency, traceroute, API health, WebSocket check)
- Probe ports and services (port check, multi-port nmap check, banner grab)
- Verify page content and browse from a region via geo-proxy, with optional screenshots
- Review quota, tier and proxy token state through account status and usage resources
- When to use it
- Useful when you need to see how a site, DNS record or endpoint behaves from several parts of the world rather than from your own machine — for example checking DNS propagation, certificate expiry, regional outages or latency differences.
- Requirements
- Local Node.js 18 or newer, run via npx. An optional PROBEOPS_API_KEY unlocks all tools and more regions; without it the server runs in demo mode. An optional PROBEOPS_BASE_URL points at a staging or self-hosted instance. Playwright with Chromium is optional and only needed for geo_browse screenshots. Network access to the ProbeOps service is required.
Installation
In SourceWeft
- Open Probeops Mcp Server in the dashboard and add it to a workspace.
- 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
ProbeOps MCP Server
[npm version] [License: MIT] [Node.js] [MCP]
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.
Works instantly — no API key required. Run npx @probeops/mcp-server and get 11 diagnostic tools with 10 free calls per day. Add an API key to unlock all 21 tools, 6 regions, and higher limits.
Works with Claude Code, Codex, Cursor, Windsurf, Cline, and any Model Context Protocol compatible client.
Quick Start
Option 1: Try It Now (No API Key)
Claude Code:
Codex:
Cursor / Windsurf / Cline (add to .mcp.json or your client's MCP config):
That's it. You get 11 tools with 10 calls per day and 2 probe regions — no signup, no configuration.
Option 2: Full Access (Free API Key)
Sign up at probeops.com and create an API key from the dashboard. Then add it to your config:
Claude Code:
Codex (add to ~/.codex/config.toml):
Cursor / Windsurf / Cline:
Demo Mode vs Full Access
What You Get
21 infrastructure diagnostic tools, each running from up to 6 regions simultaneously. Plus geo-proxy browsing and account management.
Every diagnostic tool call returns per-region results and a quota footer showing remaining usage.
Diagnostic Tools (14)
DNS Shortcuts
These call dns_lookup with a preset record_type so you don't have to remember record type names:
Geo-Proxy Browsing
Account
Resources
Global Regions
All diagnostic tools run from these 6 regions simultaneously:
Geo-Proxy Token Management
The server manages proxy tokens automatically:
- A single token works across all 6 regions. Switching regions does not consume quota.
- Daily quota = total hours of proxy browsing per day.
- Quota resets at midnight UTC.
Output Examples
SSL Check
Ping
Whois
Environment Variables
Rate Limits
Free tier requires no credit card. Check usage anytime with account_status.
See probeops.com/pricing for current details.
Development
Test locally:
Requirements
- Node.js >= 18.0.0
- Playwright (optional) - only needed for
geo_browsescreenshots Without Playwright,geo_browsefalls back to HTTP fetch (raw HTML, no screenshots).
FAQ
Q: How is this different from running curl or dig locally?
Every check runs from 6 global regions simultaneously. You see DNS propagation, latency, and availability from the perspective of real users worldwide, not your local network.
Q: Do I need to install anything besides Node.js?
No. npx -y @probeops/mcp-server handles everything. Playwright is optional (only for geo_browse screenshots).
Q: Can I use this in CI/CD pipelines?
Yes. Set PROBEOPS_API_KEY as an environment variable and call the MCP server from any MCP-compatible tool.
Q: Is the API key sent securely?
Yes. All communication uses HTTPS. The key is sent via the X-API-Key header, never in URLs or logs.
License
MIT - see LICENSE
Links
Source: README.md at commit 489656b
Tools
0Version history
1- v1.2.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts