Observed success (share of our checks)

Each day Sato Hub calls every listed hosted MCP endpoint: an initialize handshake and a tools/list. The outcome is recorded as answered, refused (the host returned 401, 403 or 429 — a live server that declined an anonymous probe), host error, or inconclusive (a timeout or failure on Sato Hub's side). Observed success is answered checks divided by attributable checks over the rolled window, alongside the number of days observed and the current streak.

The wording is strict on purpose. One probe a day from one network cannot establish uptime; it can establish that on N days the interface answered a stranger. Inconclusive days are excluded from the denominator rather than counted against the host, and refusals are shown separately.

It is not a service-level figure, not a quality measure, and small windows are not published as findings. Read it with the day count next to it.