io.github.kumarprobeops/probeops-mcp-server
NPM · @PROBEOPS/MCP-SERVER
Network diagnostics from 6 global regions. SSL, DNS, ping, whois, traceroute, port scan, latency.
Available components
Last scanned (16 hours ago)
Scores higher than 90% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 260 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability90
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1472 tokens (~58/item across 25 items; 22 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@probeops/mcp-server@1.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_status ~47
Show your ProbeOps account status: subscription tier, diagnostic quota (minute/hour/day/month), proxy token quota, and active proxy token details. Use this to check remaining quota before running multiple tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
api_health ~55
Check API endpoint health from multiple global regions. Sends an HTTP request and reports status code, response time, and availability.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | API URL to check (e.g., "https://api.example.com/health") |
No output schema declared.
No examples provided.
banner_grab ~77
Grab the service banner from a specific port on a target from multiple global regions. Identifies service type and version.
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | yes | Port number to grab banner from (e.g., 22, 80, 443) |
| target | string | yes | Hostname or IP to check (e.g., "example.com") |
No output schema declared.
No examples provided.
caa_lookup ~56
Look up CAA (Certificate Authority Authorization) DNS records for a domain. Shows which certificate authorities are authorized to issue SSL/TLS certificates.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "example.com") |
No output schema declared.
No examples provided.
cname_lookup ~57
Look up CNAME (Canonical Name) records for a domain. Shows DNS aliases. Useful for verifying CDN configuration and subdomain routing.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or subdomain to look up (e.g., "www.example.com") |
No output schema declared.
No examples provided.
dns_lookup ~88
Look up DNS records for a domain from multiple global regions. Supports A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, and PTR record types. Useful for checking DNS propagation across regions.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "example.com") |
| record_type | string | – | DNS record type (default: A) |
No output schema declared.
No examples provided.
get_api_key ~33
Get instructions to set up your ProbeOps API key for full access to all 21 tools and 6 global regions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
is_it_down ~55
Check if a website is up, down, or partially available from multiple global regions. Returns HTTP status and response time per region.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL to check (e.g., "https://example.com") |
No output schema declared.
No examples provided.
keyword_check ~99
Check if a keyword exists in a web page's raw HTML source from multiple global regions. Searches raw HTML — does not execute JavaScript, so content rendered client-side (SPAs, dynamic widgets) may not be detected. Useful for verifying static content delivery and geo-specific content.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Keyword or phrase to search for on the page |
| url | string | yes | URL to check (e.g., "https://example.com") |
No output schema declared.
No examples provided.
latency_test ~64
Measure network latency (ping) to a target from multiple global regions. Returns per-region latency plus average, min, and max.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Hostname or IP to test (e.g., "example.com" or "8.8.8.8") |
No output schema declared.
No examples provided.
mx_lookup ~55
Look up MX (Mail Exchange) records for a domain. Shows mail servers and priorities. Useful for verifying email configuration and troubleshooting email delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "example.com") |
No output schema declared.
No examples provided.
nmap_port_check ~97
Check if multiple ports are open or closed on a target from multiple global regions using nmap. Checks specified ports (not a full scan).
| Name | Type | Req | Description |
|---|---|---|---|
| ports | string | – | Ports to check (e.g., "80,443" or "22,80,443,8080"). Default: common ports 1-1024 |
| target | string | yes | Hostname or IP to check (e.g., "example.com") |
No output schema declared.
No examples provided.
ns_lookup ~54
Look up NS (Nameserver) records for a domain. Shows authoritative DNS servers. Useful for verifying DNS delegation and nameserver configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "example.com") |
No output schema declared.
No examples provided.
ping ~64
ICMP ping a target from multiple global regions. Returns packet loss and round-trip times. Useful for basic reachability and latency testing.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Hostname or IP to ping (e.g., "example.com" or "8.8.8.8") |
No output schema declared.
No examples provided.
port_check ~73
Check if a specific port is open, closed, or filtered on a target from multiple global regions. Useful for verifying firewall rules and service availability.
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | yes | Port number to check (1-65535) |
| target | string | yes | Hostname or IP to check (e.g., "example.com") |
No output schema declared.
No examples provided.
reverse_dns_lookup ~63
Perform reverse DNS (PTR) lookup for an IP address. Finds the hostname associated with an IP. Essential for email deliverability verification and server identification.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IP address to look up (e.g., "8.8.8.8") |
No output schema declared.
No examples provided.
ssl_check ~62
Check SSL/TLS certificate for a domain from multiple global regions. Returns certificate details (validity, expiry, issuer, TLS version, SANs) and checks consistency across regions.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to check (e.g., "example.com") |
No output schema declared.
No examples provided.
tcp_ping ~75
Measure TCP-level latency to a specific port on a target from multiple global regions. More reliable than ICMP ping for hosts that block ICMP.
| Name | Type | Req | Description |
|---|---|---|---|
| port | integer | yes | Port number to TCP ping (e.g., 443) |
| target | string | yes | Hostname or IP to test (e.g., "example.com") |
No output schema declared.
No examples provided.
traceroute ~72
Trace the network path to a target from one or more global regions. Shows each hop with latency. Supports TCP, UDP, and ICMP protocols.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | – | Protocol to use (default: tcp) |
| target | string | yes | Hostname or IP to trace (e.g., "example.com") |
No output schema declared.
No examples provided.
txt_lookup ~61
Look up TXT records for a domain. Shows SPF, DKIM, DMARC, domain verification, and other TXT records. Essential for email authentication and domain ownership verification.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "example.com") |
No output schema declared.
No examples provided.
websocket_check ~54
Check WebSocket endpoint health and connectivity from multiple global regions. Verifies that a WebSocket server is accepting connections.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | WebSocket URL to check (e.g., "wss://example.com/ws") |
No output schema declared.
No examples provided.
whois ~53
Look up WHOIS registration information for a domain. Shows registrar, creation/expiry dates, nameservers, and registrant info.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to look up (e.g., "example.com") |
No output schema declared.
No examples provided.
How do I install the io.github.kumarprobeops/probeops-mcp-server server?
io.github.kumarprobeops/probeops-mcp-server runs locally as an npm package, launched with npx -y @probeops/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @probeops/mcp-server
claude mcp add kumarprobeops-probeops-mcp-server -- npx -y @probeops/mcp-server
What is the io.github.kumarprobeops/probeops-mcp-server server?
io.github.kumarprobeops/probeops-mcp-server is listed in the public MCP registry as io.github.kumarprobeops/probeops-mcp-server. Network diagnostics from 6 global regions. SSL, DNS, ping, whois, traceroute, port scan, latency. This page covers its npm package (@probeops/mcp-server).
Is the io.github.kumarprobeops/probeops-mcp-server server safe to use?
io.github.kumarprobeops/probeops-mcp-server scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.kumarprobeops/probeops-mcp-server server expose?
io.github.kumarprobeops/probeops-mcp-server exposes 22 tools: ssl_check, dns_lookup, mx_lookup, txt_lookup, ns_lookup, and 17 more. Their descriptions and schemas cost roughly 1,414 tokens of context every time the server is loaded.
Is the io.github.kumarprobeops/probeops-mcp-server server still maintained?
io.github.kumarprobeops/probeops-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.kumarprobeops/probeops-mcp-server server under?
io.github.kumarprobeops/probeops-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.kumarprobeops/probeops-mcp-server server?
VerifyMCP ran 16 checks on io.github.kumarprobeops/probeops-mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.