Sato Hub
MCP server status

Allium MCP

The result of our last daily check against its MCP endpoint.

  • Live, but refused our check (HTTP 401)
  • Checks succeeded70%

https://mcp.allium.so

Live, but refused our check (HTTP 401)
Last check
Sat, 24 Oct 2026 05:27 UTC
Method
MCP initialize + tools/list
Tools listed
48 (from the server's own tools/list)
Detail
refused our check (HTTP 401)

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

2 succeeded · 0 host errors · 28 no check or unattributable. Over 90 days since 2026-07-26: 70% of our checks succeeded.

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

69.2%of 91 checks since 2026-07-26 succeeded
Currently unreachable from our probe for 27 days
Succeeded
63
Failed
28
Their error
0
Unattributed
28

State changed on 2026-09-25 (responding → unreachable from our probe), 2026-09-26 (unreachable from our probe → responding), 2026-09-28 (responding → unreachable from our probe).

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

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 8/30 days
Tools listed
48
from the server's own tools/list · 29/30 days
Sato Score
39
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-26

  • 2026-09-23 47 → 48 +1 (search_dashboards)
  • 2026-09-21 46 → 47 +25 (get_realtime_crosschain_assets, get_realtime_holdings_history, get_realtime_holdings_pnl, get_realtime_holdings_pnl_by_token…) −24 (realtime_fills, realtime_get_assets, realtime_get_positions, realtime_get_supported_chains…)
  • 2026-09-04 48 → 46 −2 (share_dashboard, share_explorer_query)
  • 2026-08-12 47 → 48 +1 (list_compute_profiles)
  • 2026-08-05 43 → 47 +5 (create_explorer_visual, delete_explorer_visual, get_explorer_visual, get_terminal_results…) −1 (create_explorer_chart)

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.

Embed this status badge

MCP status on Sato Hub badge previewLive preview
[![MCP status on Sato Hub](https://satohub.ai/api/badge/status/allium-mcp)](https://satohub.ai/status/allium-mcp?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 pageShowHide

Cite this page

Sato Hub. "Allium MCP MCP endpoint — daily check record." Sato Hub, updated 2026-10-24, accessed 2026-10-24. https://satohub.ai/status/allium-mcp

Data last refreshed 2026-10-24; 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.