Remote MCP · Endpoint

MacroCyber MCP server

No. MacroCyber answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://macrocyber.co/api/mcp

The last check completed an MCP handshake.

Registry name
co.macrocyber/attack-surface
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Scan a site or AI-built app for exposed databases, keys and MCP endpoints, then verify the fixes.
Listing
From the official MCP registry (active).
Recent checks of MacroCyber
CheckedResultHandshake
56 minutes agoHandshake completed117 ms
3 days agoHandshake completed107 ms
12 days agoHandshake completed180 ms
13 days agoHandshake completed151 ms
15 days agoHandshake completed250 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed146 ms
18 days agoHandshake completed101 ms
18 days agoHandshake completed132 ms
20 days agoHandshake completed151 ms
22 days agoHandshake completed234 ms
25 days agoHandshake completed100 ms
27 days agoHandshake completed173 ms
29 days agoHandshake completed113 ms

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

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 MacroCyber and makes no claim about it beyond what these checks measured.