Probeops MCP Server

Name: Probeops MCP Server
Author: kumarprobeops

作者：kumarprobeops版本 1.2.3i★ –i在你的电脑上运行

注册名称io.github.kumarprobeops/probeops-mcp-server

安装

概览

作者提供的说明（英文原文）

Network diagnostics from 6 global regions. SSL, DNS, ping, whois, traceroute, port scan, latency.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：PROBEOPS_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PROBEOPS_API_KEY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

claude mcp add probeops --env PROBEOPS_API_KEY=your-value -- npx -y @probeops/mcp-server

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "probeops": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@probeops/mcp-server"
      ],
      "env": {
        "PROBEOPS_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PROBEOPS_API_KEY 机密 env
ProbeOps API key (optional, runs in demo mode without it)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 kumarprobeops 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32435 个服务器的 0%
发布到注册中心的时间比此分类中其他 32435 个服务器的 2% 更新
基础检查结果等于或优于此分类中其他 32435 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Probeops MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：PROBEOPS_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.2.3）于9个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Apify MCP Server

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

Apify MCP Server

作者：apify

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

ProbeOps MCP Server

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:

claude mcp add probeops -- npx -y @probeops/mcp-server

Codex:

codex mcp add probeops -- npx -y @probeops/mcp-server

Cursor / Windsurf / Cline (add to .mcp.json or your client's MCP config):

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

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)

Claude Code:

claude mcp add probeops -e PROBEOPS_API_KEY=your-key -- npx -y @probeops/mcp-server

Codex (add to ~/.codex/config.toml):

[mcp_servers.probeops]

command = "npx" args = ["-y", "@probeops/mcp-server"]

[mcp_servers.probeops.env] PROBEOPS_API_KEY = "your-api-key-here"

Cursor / Windsurf / Cline:

"mcpServers": { "probeops": { "command": "npx", "args": ["-y", "@probeops/mcp-server"], "env": { "PROBEOPS_API_KEY": "your-api-key-here" } } } }

Demo Mode vs Full Access

	Demo Mode (no key)	Free Tier (with key)	Professional
Tools	11	21	21
Calls per day	10	100	5,000
Regions per call	2	4	6
Geo-proxy browsing	—	3 hours/day	10 hours/day
Setup time	0 min	2 min	2 min

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)

Tool	What it does	Example input
`ssl_check`	SSL/TLS certificate validity, expiry, issuer, TLS version, SANs, cross-region consistency	`{ "domain": "example.com" }`
`dns_lookup`	DNS record lookup (A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, PTR) with multi-region propagation check	`{ "domain": "example.com", "record_type": "MX" }`
`is_it_down`	Website up/down/partial status from multiple regions	`{ "url": "https://example.com" }`
`latency_test`	HTTP latency (TTFB) from multiple regions, returns min/avg/max	`{ "target": "example.com" }`
`traceroute`	Network path tracing with per-hop latency. TCP, UDP, or ICMP	`{ "target": "example.com", "protocol": "tcp" }`
`port_check`	Port open/closed/filtered check from multiple regions	`{ "target": "example.com", "port": 443 }`
`ping`	ICMP ping with packet loss and round-trip times	`{ "target": "8.8.8.8" }`
`whois`	Domain registration info: registrar, dates, nameservers	`{ "domain": "example.com" }`
`nmap_port_check`	Check multiple ports open/closed using nmap (not a full scan)	`{ "target": "example.com", "ports": "80,443" }`
`tcp_ping`	TCP-level latency to a specific port (works when ICMP is blocked)	`{ "target": "example.com", "port": 443 }`
`keyword_check`	Check if a keyword exists on a web page from multiple regions	`{ "url": "https://example.com", "keyword": "pricing" }`
`websocket_check`	WebSocket endpoint connectivity check	`{ "url": "wss://example.com/ws" }`
`banner_grab`	Service banner/version detection on a port	`{ "target": "example.com", "port": 22 }`
`api_health`	API endpoint health check (HTTP status, response time, availability)	`{ "url": "https://api.example.com/health" }`

DNS Shortcuts

These call dns_lookup with a preset record_type so you don't have to remember record type names:

Tool	Equivalent to
`mx_lookup`	`dns_lookup` with `record_type: "MX"`
`txt_lookup`	`dns_lookup` with `record_type: "TXT"`
`ns_lookup`	`dns_lookup` with `record_type: "NS"`
`cname_lookup`	`dns_lookup` with `record_type: "CNAME"`
`caa_lookup`	`dns_lookup` with `record_type: "CAA"`
`reverse_dns_lookup`	`dns_lookup` with `record_type: "PTR"` (takes an IP address)

Geo-Proxy Browsing

Tool	What it does	Example input
`get_geo_proxy`	Get proxy credentials for a region. Use with Playwright or any HTTPS proxy client	`{ "region": "eu-central" }`
`geo_browse`	Browse a URL from a region using a real browser. Returns page content and/or screenshot	`{ "url": "https://example.com", "region": "ap-south" }`

Account

Tool	What it does
`account_status`	Current quota usage (minute/hour/day/month), subscription tier, active proxy token

Resources

URI	Description
`probeops://regions`	Probe regions with location, country, and node count
`probeops://proxy-regions`	Geo-proxy regions with FQDNs and proxy URLs
`probeops://usage`	Current API usage, remaining quota, active token status

Global Regions

All diagnostic tools run from these 6 regions simultaneously:

Region Code	Location	Country
`us-east`	Ashburn, Virginia	United States
`us-west`	Boardman, Oregon	United States
`eu-central`	Helsinki	Finland
`ca-central`	Montreal	Canada
`ap-south`	Mumbai	India
`ap-southeast`	Sydney	Australia

Geo-Proxy Token Management

The server manages proxy tokens automatically:

Token State	Action	Quota Cost
> 5 min remaining	Reuse cached token	0
0-5 min remaining	Auto-extend +1 hour	1 unit
Expired or no token	Generate new token	1 unit

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

ssl_check({ domain: "github.com" })

SSL Certificate Report for github.com Status: VALID Subject: github.com Issuer: DigiCert (DigiCert Inc) Expires in: 245 days TLS: TLSv1.3 (TLS_AES_256_GCM_SHA384)

Region Results:

Region	Location	Status	Time
us-east	Ashburn	OK	45ms
eu-central	Helsinki	OK	38ms
ap-south	Mumbai	OK	112ms
us-west	Boardman	OK	52ms
ca-central	Montreal	OK	41ms
ap-southeast	Sydney	OK	98ms

Completed in 125ms

Diagnostics: 97 of 100 remaining today (Free)

Ping

ping({ target: "1.1.1.1" })

Ping: 1.1.1.1

ap-south (Mumbai): PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=1.35 ms 3 packets transmitted, 3 received, 0% packet loss rtt min/avg/max/mdev = 1.353/1.398/1.474/0.054 ms Response time: 2147ms

eu-central (Helsinki): PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=54 time=21.2 ms 3 packets transmitted, 3 received, 0% packet loss rtt min/avg/max/mdev = 20.651/20.941/21.217/0.231 ms Response time: 2031ms ...

Completed in 2332ms

Diagnostics: 96 of 100 remaining today (Free)

Whois

whois({ domain: "example.com" })

Whois: example.com

us-east (Ashburn): Domain Name: EXAMPLE.COM Registry Domain ID: 2336799_DOMAIN_COM-VRSN Registrar: RESERVED-Internet Assigned Numbers Authority Creation Date: 1995-08-14T04:00:00Z Registry Expiry Date: 2025-08-13T04:00:00Z Name Server: A.IANA-SERVERS.NET Name Server: B.IANA-SERVERS.NET DNSSEC: signedDelegation Response time: 734ms ...

Completed in 852ms

Diagnostics: 95 of 100 remaining today (Free)

Environment Variables

Variable	Required	Default	Description
`PROBEOPS_API_KEY`	No	-	Your ProbeOps API key (get one free). Without it, runs in demo mode (11 tools, 10 calls/day)
`PROBEOPS_BASE_URL`	No	`https://probeops.com`	API base URL (for staging or self-hosted instances)

Rate Limits

	Free	Standard	Professional
Per minute	15	30	50
Per hour	100	500	2,000
Per day	100	1,000	5,000
Per month	500	20,000	100,000
Concurrent	3	5	10
Proxy hours/day	3	5	10
Regions	4 of 6	All 6	All 6

Free tier requires no credit card. Check usage anytime with account_status.

See probeops.com/pricing for current details.

Development

git clone https://github.com/kumarprobeops/probeops-mcp-server.git

cd probeops-mcp-server npm install npm run build

Test locally:

PROBEOPS_API_KEY=your-key node dist/index.js

Requirements

Node.js >= 18.0.0
Playwright (optional) - only needed for geo_browse screenshots

  npx playwright install chromium

Without Playwright, geo_browse falls 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