Live Papertrade liquidation map, heatmap and closest-to-bust feed with a JSON AP
Live Papertrade liquidation map, heatmap and closest-to-bust feed with a JSON API and read-only MCP server.
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://papertrade-liquidations.pages.dev/mcp |
|---|---|
| Source | https://github.com/nirholas/papertrade-liquidations |
| Transport | http |
| Tools | 5 |
| Auth | none |
| First seen | 2026-11-11 01:34:46 |
| Last checked | 2026-11-17 21:56:22 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 311 / 516 ms |
| Last successful check | 2026-11-17 21:56:22 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (5)
get_bust_map— Liquidation (bust) map for BTC or ETH on Papertrade: notional that busts at each price bucket, split into long busts below the mark and shorget_closest_to_bust— The open Papertrade positions closest to their bust price right now, nearest first, across BTC and ETH or one market. Each row has side, levget_bust_cluster_summary— Where liquidations cluster for a market: the largest groups of neighbouring bust prices on each side of the mark with their notional, positiget_wallet_distance_to_bust— Distance to bust for every open Papertrade position of one wallet address: side, leverage, margin, notional, entry, bust price, the live marget_protocol_liquidation_map— The whole-protocol liquidation map published by the Papertrade API: every open position, not just the largest wallets, in buckets around the
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:56:22 | ✓ | ✓ | 334 ms | 90 | active |
| 2026-11-17 21:41:07 | ✓ | ✓ | 445 ms | 90 | active |
| 2026-11-17 21:25:53 | ✓ | ✓ | 299 ms | 94 | active |
| 2026-11-17 21:10:42 | ✓ | ✓ | 356 ms | 90 | active |
| 2026-11-17 20:55:39 | ✓ | ✓ | 510 ms | 90 | active |
| 2026-11-17 20:40:36 | ✓ | ✓ | 530 ms | 90 | active |
| 2026-11-17 20:25:33 | ✓ | ✓ | 669 ms | 90 | active |
| 2026-11-17 20:10:17 | ✓ | ✓ | 256 ms | 94 | active |
| 2026-11-17 19:54:32 | ✓ | ✓ | 391 ms | 90 | active |
| 2026-11-17 19:39:26 | ✓ | ✓ | 412 ms | 90 | active |
| 2026-11-17 19:24:06 | ✓ | ✓ | 404 ms | 90 | active |
| 2026-11-17 19:08:59 | ✓ | ✓ | 376 ms | 90 | active |
| 2026-11-17 18:53:40 | ✓ | ✓ | 294 ms | 94 | active |
| 2026-11-17 18:38:39 | ✓ | ✓ | 358 ms | 90 | active |
| 2026-11-17 18:23:34 | ✓ | ✓ | 399 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://papertrade-liquidations.pages.dev/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/papertrade-liquidations-pages-dev-mcp # JSON