Status

Sato Hub API status

Name: Sato Hub machine-surface availability
Creator: Sato Hub
License: https://creativecommons.org/licenses/by/4.0/

See whether the Sato Hub MCP server and data feeds answered our hourly check.

Get the data MCP servers we list

Checked2026-10-29

What this record meansShowHide

Sato Hub checks its own machine surfaces once an hour and publishes the result. Each row is the share of our checks that succeeded and how long they took: one checker, one region. A failed check may be the surface, the network in between, or the checker itself, and we cannot tell which. This is a record, not a service-level agreement.

Availability is not usage. Nothing here counts requests anyone else made. Looking for the MCP servers we list? That is /status.

MCP initialize

/api/mcpOperational

JSON-RPC initialize handshake

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 569ms
Last checked:: 2026-10-29 02:20 UTC

MCP tools/list

/api/mcpOperational

JSON-RPC tools/list returns a non-empty tool set

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 365ms
Last checked:: 2026-10-29 02:20 UTC

MCP tools/call

/api/mcpOperational

one search call through onchain_agent_search_resources

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 1.11s
Last checked:: 2026-10-29 02:20 UTC

Directory export

/api/export/index.jsonOperational

GET, parsed, entry list non-empty

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 898ms
Last checked:: 2026-10-29 02:20 UTC

Change feed

/api/changesOperational

GET with a 7-day window, parsed

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 1.32s
Last checked:: 2026-10-29 02:20 UTC

Preflight

/api/preflightOperational

GET one fixed token target, verdict present

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 1.65s
Last checked:: 2026-10-29 02:20 UTC

Signing JWKS

/.well-known/jwks.jsonOperational

GET, one Ed25519 key present

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 293ms
Last checked:: 2026-10-29 02:20 UTC

Response signature

/.well-known/jwks.jsonOperational

the Preflight body verified against the published JWKS key

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 2ms
Last checked:: 2026-10-29 02:20 UTC

OpenAPI document

/api/openapi.jsonOperational

GET, parsed, paths present

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 372ms
Last checked:: 2026-10-29 02:20 UTC

Score badge

/api/badge/{slug}Operational

GET one listing badge, SVG returned

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 400ms
Last checked:: 2026-10-29 02:20 UTC

Agent manifest

/api/agents/{slug}/manifestOperational

GET one passport manifest, parsed

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 632ms
Last checked:: 2026-10-29 02:20 UTC

Route quote

/api/route/swapOperational

GET one swap quote, response parsed

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 1.95s
Last checked:: 2026-10-29 02:20 UTC

llms.txt

/llms.txtOperational

GET, non-empty body

Checks that succeeded, 90d:: 100.0%
p95 latency, typical day:: 286ms
Last checked:: 2026-10-29 02:20 UTC

Incidents

An incident opens when 3 consecutive checks of one surface fail, and closes on the first check that succeeds. Derived from the last 14 days of checks — nobody declares one, and there is no place to write a note about one.

No run of 3 consecutive failures in the last 14 days.

How these numbers are madeShowHide

One checker, hourly, from a GitHub Actions runner. Not a distributed probe network.
A percentage is withheld until a surface has 24 checks in the window — the same sample-size rule the rest of the catalog keeps. Withheld reads as withheld, never as 100%.
Latency percentiles use successful checks only. A timed-out request records a deadline, not a measurement of the surface, and would drag a percentile toward the timeout.
The window figure is the median of the daily p95s. Averaging percentiles produces a number that describes nothing; naming the statistic is cheaper than explaining it later.
The signature row verifies a signed response against the key published at /.well-known/jwks.json, the way an outside consumer would — never against a local key.
Days with no checks are drawn as gaps. A day we did not run is not a day at 100%.

Machine-readable: /api/status.json (current), /status/history.json (daily rollups), /status/feed.xml (incident feed). Report assembled 2026-10-29 07:21 UTC.