EruditePay Blockchain Intelligence
The result of our last daily check against its MCP endpoint.
- Answering — MCP handshake succeeded
- Checks succeeded46.9%
https://bridge.eruditepay.com/mcp
- Last check
- Thu, 08 Oct 2026 05:26 UTC
- Method
- MCP initialize + tools/list
- Tools listed
- 6 (from the server's own tools/list)
- Chain data
- One read-only tool call returned data — tools/call intel_gas with no arguments. A handshake is not evidence the chain reads still work; this says nothing about the data being correct.
Last 30 days of our checks · oldest → newest, to 2026-10-08
0 succeeded · 29 host errors · 1 no check or unattributable. Over 81 observed days: 46.9% of our checks succeeded.
Observed record — 82 daily checks since 2026-07-19
- Succeeded
- 39
- Failed
- 43
- Their error
- 34
- Unattributed
- 9
State changed on 2026-08-24 (responding → unclear), 2026-08-26 (unclear → responding), 2026-09-04 (responding → failing), 2026-10-08 (failing → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 44 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Rates spanning that date mix two definitions. Since then: 10.5%.
Last 30 days — to 2026-10-08, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Embed this status badge
[](https://satohub.ai/status/eruditepay-blockchain-intelligence?utm_source=badge&utm_medium=embed)Paste into your README. The badge shows the result of Sato Hub's own daily check and links back to this page. It is not an uptime guarantee, and it says nothing about the server's safety or quality. Free to use, no attribution required.
This is the record of Sato Hub's own daily check, not the server's uptime. A failure we cannot attribute to the host is not proof it was down; a 401/403/429 is a live server that refused our runner. Failures before 2026-09-01 were recorded without a cause. Nothing here is a statement about the server's safety or quality.
Listing → · Sato Score report → · Reliability index →
Reference
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "EruditePay Blockchain Intelligence MCP endpoint — daily check record." Sato Hub, updated 2026-10-08, accessed 2026-10-08. https://satohub.ai/status/eruditepay-blockchain-intelligenceData last refreshed 2026-10-08; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.