The official Model Context Protocol (MCP) server for BackPow - The Proof of Work
The official Model Context Protocol (MCP) server for BackPow - The Proof of Work Oracle
active Production-safe Score 97/100 http no auth
At a glance
| Endpoint | https://mcp.backpow.com/mcp |
|---|---|
| Source | https://github.com/BackpowCom/backpow-mcp-server |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-09-26 18:58:56 |
| Last checked | 2026-11-17 21:49:17 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 199 / 434 ms |
| Last successful check | 2026-11-17 21:49:17 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
calculate_solo_mining_odds— Probability of a solo miner finding a block, computed as a Poisson process over live network difficulty and hashrate, plus the electricity cget_cost_of_production— Cost of Production (CoP) for one Proof of Work coin: the all-in electricity cost of mining one unit on the most efficient hardware BackPow tget_coin_oracle— Current network state for one Proof of Work chain, measured by BackPow's stratum collector nodes: difficulty, derived network hashrate, bloclist_pow_coins— Paginated index of the Proof of Work networks BackPow tracks, with algorithm, network rate, collector status and canonical page URL. Optionaget_hardware_benchmarks— Mining hardware matched to the coins it can mine, ranked by net USD per day at a given electricity rate. Covers ASICs, GPUs and CPUs, with hget_pow_news— Recent news items about Proof of Work mining and network events, optionally filtered to one coin. Items are aggregated from third-party feed
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:49:17 | ✓ | ✓ | 184 ms | 94 | active |
| 2026-11-17 21:34:11 | ✓ | ✓ | 151 ms | 94 | active |
| 2026-11-17 21:19:00 | ✓ | ✓ | 203 ms | 94 | active |
| 2026-11-17 21:03:54 | ✓ | ✓ | 197 ms | 94 | active |
| 2026-11-17 20:48:37 | ✓ | ✓ | 253 ms | 94 | active |
| 2026-11-17 20:33:32 | ✓ | ✓ | 350 ms | 91 | active |
| 2026-11-17 20:18:30 | ✓ | ✓ | 426 ms | 91 | active |
| 2026-11-17 20:03:00 | ✓ | ✓ | 175 ms | 94 | active |
| 2026-11-17 19:47:33 | ✓ | ✓ | 295 ms | 94 | active |
| 2026-11-17 19:32:28 | ✓ | ✓ | 365 ms | 91 | active |
| 2026-11-17 19:17:22 | ✓ | ✓ | 205 ms | 94 | active |
| 2026-11-17 19:01:48 | ✓ | ✓ | 188 ms | 94 | active |
| 2026-11-17 18:46:44 | ✓ | ✓ | 153 ms | 94 | active |
| 2026-11-17 18:31:43 | ✓ | ✓ | 141 ms | 94 | active |
| 2026-11-17 18:16:41 | ✓ | ✓ | 194 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.backpow.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-backpow-com-mcp # JSON