Remote MCP · Endpoint

CyberMax Data MCP server

No. CyberMax Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://data.cybermax-tools.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.shawmena-dotcom/cybermax-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free US data lookups: ZIP demographics, CISA KEV/EPSS CVEs, domain rank, county spending, recalls.
Listing
From the official MCP registry (active).
Recent checks of CyberMax Data
CheckedResultHandshake
1 hour agoHandshake completed93 ms
2 days agoHandshake completed350 ms
4 days agoHandshake completed105 ms
6 days agoHandshake completed152 ms
7 days agoHandshake completed104 ms
9 days agoHandshake completed114 ms
10 days agoHandshake completed299 ms
11 days agoHandshake completed54 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed57 ms
17 days agoHandshake completed88 ms
18 days agoHandshake completed109 ms
20 days agoHandshake completed58 ms
21 days agoHandshake completed59 ms
22 days agoHandshake completed72 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CyberMax Data and makes no claim about it beyond what these checks measured.