Remote MCP · Endpoint

Deltawren MCP server

No. Deltawren answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://deltawren.cybermaxtools.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/deltawren
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
137 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Daily data feeds MCP: CISA KEV+EPSS, SEC Form 4, 10-K sections, domain ranks. Keys $19/mo.
Listing
From the official MCP registry (active).
Recent checks of Deltawren
CheckedResultHandshake
1 hour agoHandshake completed137 ms
1 day agoHandshake completed150 ms
2 days agoHandshake completed71 ms
2 days agoHandshake completed43 ms
4 days agoHandshake completed111 ms
7 days agoHandshake completed103 ms
9 days agoHandshake completed114 ms
12 days agoHandshake completed88 ms
14 days agoHandshake completed110 ms
16 days agoHandshake completed170 ms
18 days agoHandshake completed1.36 s
20 days agoHandshake completed56 ms
22 days agoHandshake completed72 ms
24 days agoHandshake completed58 ms

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

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