Sato Hub

Status · MCP server

Is the Avalanche Builder Hub MCP MCP server answering?

https://build.avax.network/api/mcp

Answering — MCP handshake succeeded
Last check
Tue, 08 Sep 2026 21:08 UTC
Method
MCP initialize + tools/list
Tools listed
48 (from the server's own tools/list)

Last 30 days of our checks · oldest → newest, to 2026-09-09

29 succeeded · 0 host errors · 1 no check or unattributable. Over 57 observed days: 100% of our checks succeeded.

Observed record 57 daily checks since 2026-07-14

100%of our checks succeeded
Currently responding for 57 days
Succeeded
57
Failed
0
Their error
0
Unattributed
0

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. 49 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: 100%.

Last 30 days — to 2026-09-09, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
48
from the server's own tools/list · 29/30 days
Sato Score
65
as snapshotted that day · 29/30 days

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 48 now, peak 48, since 2026-07-14

  • 2026-07-29 4448 +7 (build_plan, chain_stats, console_flow, console_link) 3 (github_get_file, github_list_repositories, github_search_code)

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.

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 →

Cite this page

Sato Hub. "Avalanche Builder Hub MCP MCP endpoint — daily check record." Sato Hub, updated 2026-09-08, accessed 2026-09-09. https://satohub.ai/status/avalanche-mcp

This page is refreshed daily. Citations include the date so a reader can tell which snapshot a claim came from.