Status · MCP server
Is the Skim MCP server answering?
https://skim402.com/mcp
- Last check
- Wed, 23 Sep 2026 13:37 UTC
- Method
- MCP initialize + tools/list
- Tools listed
- 3 (from the server's own tools/list)
- Chain data
- Not checked — chain-data check skipped: no chain-data tool advertised. A handshake is not evidence the chain reads still work; this says nothing about the data being correct.
Observed record — 1 daily check since 2026-09-23
- Succeeded
- 1
- 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.
Embed this status badge
[](https://satohub.ai/status/skim?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 →
Cite this page
Sato Hub. "Skim MCP endpoint — daily check record." Sato Hub, updated 2026-09-23, accessed 2026-09-23. https://satohub.ai/status/skimData last refreshed 2026-09-23; 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.