Remote MCP · Endpoint
Dragons Eye Ransomware Claims MCP server
No. Dragons Eye Ransomware Claims answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.ransomware-tracker.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.ransomware-tracker.api/dragonseye
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 273 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 15 checks
- Described by its publisher as
- Ransomware claim lookups, IOC and CVE intel, group intel, bulk checks and watch alerts (x402 USDC).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 273 ms |
| 1 day ago | Handshake completed | 371 ms |
| 2 days ago | Handshake completed | 400 ms |
| 3 days ago | Handshake completed | 202 ms |
| 4 days ago | Handshake completed | 104 ms |
| 5 days ago | Handshake completed | 297 ms |
| 7 days ago | Handshake completed | 269 ms |
| 10 days ago | Handshake completed | 298 ms |
| 12 days ago | Handshake completed | 223 ms |
| 14 days ago | Handshake completed | 488 ms |
| 17 days ago | Handshake completed | 397 ms |
| 19 days ago | Handshake completed | 228 ms |
| 21 days ago | Handshake completed | 192 ms |
| 23 days ago | Handshake completed | 295 ms |
| 25 days ago | Handshake completed | 216 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 Dragons Eye Ransomware Claims and makes no claim about it beyond what these checks measured.