deBridge MCP

Observed record — 91 daily checks since 2026-07-26

Succeeded

90

Failed

1

Their error

0

Unattributed

1

State changed on 2026-09-04 (responding → unreachable from our probe), 2026-09-05 (unreachable from our probe → 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. 37 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. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-24, 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.

Tool inventory history — 5 now, peak 5, since 2026-07-26

• 2026-09-23 0 → 5 +5 (create_tx, get_instructions, get_supported_chains, search_tokens…)

Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.