Status · MCP server

Is the Alby MCP MCP server answering?

Name: Alby MCP MCP endpoint — Sato Hub daily check record
Creator: Sato Hub
License: https://creativecommons.org/licenses/by/4.0/

https://mcp.getalby.com/mcp

Not answering — the host returned an error to our check

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

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

0 succeeded · 8 host errors · 22 no check or unattributable. Over 57 observed days: 8.8% of our checks succeeded.

Observed record — 57 daily checks since 2026-07-14

8.8%of our checks succeeded

Currently failing for 8 days

Succeeded: 5
Failed: 52
Their error: 8
Unattributed: 44

State changed on 2026-07-19 (responding → unclear), 2026-09-01 (unclear → failing).

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: 0%.

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

Share of OUR checks that succeeded

7-day rolling; unattributable days are gaps · 9/30 days

Tools listed

fewer than 2 points—

from the server's own tools/list · 0/30 days

Sato Score

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.

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. "Alby MCP MCP endpoint — daily check record." Sato Hub, updated 2026-09-08, accessed 2026-09-09. https://satohub.ai/status/alby-mcp

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