Sato Hub
← Crypto APIs MCP Servers verification record

Score history

Crypto APIs MCP Servers

Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.

Score today

63

Change over 62d

+3

Days measured

62

Days missed

0

Sato Score, daily

2026-07-14 → 2026-09-13
02550751002026-07-15: Sato Hub changed the scoring method (60 → 61). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (61 → 63). Not a change by the project.2026-07-14: 60 (Medium)2026-07-15: 61 (Medium)2026-07-16: 61 (Medium)2026-07-17: 61 (Medium)2026-07-18: 61 (Medium)2026-07-19: 61 (Medium)2026-07-20: 61 (Medium)2026-07-21: 61 (Medium)2026-07-22: 61 (Medium)2026-07-23: 61 (Medium)2026-07-24: 61 (Medium)2026-07-25: 61 (Medium)2026-07-26: 61 (Medium)2026-07-27: 61 (Medium)2026-07-28: 61 (Medium)2026-07-29: 61 (Medium)2026-07-30: 61 (Medium)2026-07-31: 61 (Medium)2026-08-01: 61 (Medium)2026-08-02: 61 (Medium)2026-08-03: 61 (Medium)2026-08-04: 39 (Low)2026-08-05: 61 (Medium)2026-08-06: 61 (Medium)2026-08-07: 61 (Medium)2026-08-08: 61 (Medium)2026-08-09: 61 (Medium)2026-08-10: 61 (Medium)2026-08-11: 61 (Medium)2026-08-12: 61 (Medium)2026-08-13: 61 (Medium)2026-08-14: 61 (Medium)2026-08-15: 61 (Medium)2026-08-16: 61 (Medium)2026-08-17: 61 (Medium)2026-08-18: 61 (Medium)2026-08-19: 61 (Medium)2026-08-20: 61 (Medium)2026-08-21: 61 (Medium)2026-08-22: 61 (Medium)2026-08-23: 61 (Medium)2026-08-24: 61 (Medium)2026-08-25: 61 (Medium)2026-08-26: 61 (Medium)2026-08-27: 61 (Medium)2026-08-28: 61 (Medium)2026-08-29: 61 (Medium)2026-08-30: 61 (Medium)2026-08-31: 61 (Medium)2026-09-01: 63 (Medium)2026-09-02: 63 (Medium)2026-09-03: 63 (Medium)2026-09-04: 63 (Medium)2026-09-05: 63 (Medium)2026-09-06: 63 (Medium)2026-09-07: 63 (Medium)2026-09-08: 63 (Medium)2026-09-09: 63 (Medium)2026-09-10: 63 (Medium)2026-09-11: 63 (Medium)2026-09-12: 63 (Medium)2026-09-13: 63 (Medium)6063632026-07-142026-09-13

Every day in this span has a reading. A dashed vertical mark (┆) is a day Sato Hub changed the scoring method — movement on those days is ours, not the project’s.

Every day the score moved

2 changes attributable to the project, 2 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-016163+2Sato Hub changed the scoring method
2026-08-053961+22the project
2026-08-046139-22the project
2026-07-156061+1Sato Hub changed the scoring method

What moved, component by component

Six charts, six axes — each scaled to its own maximum weight. They are never stacked on one axis: a component worth 10 points and one worth 35 would not be comparable on a shared scale, and the small one is usually the one that moved.

Maintenance & liveness35/35
35
Code transparency8/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification2/10
10

The observed record

98.4% of Sato Hub's own daily checks succeeded over 62 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.

2026-07-14: answered our check2026-07-15: answered our check2026-07-16: answered our check2026-07-17: answered our check2026-07-18: answered our check2026-07-19: answered our check2026-07-20: answered our check2026-07-21: answered our check2026-07-22: answered our check2026-07-23: answered our check2026-07-24: answered our check2026-07-25: answered our check2026-07-26: answered our check2026-07-27: answered our check2026-07-28: answered our check2026-07-29: answered our check2026-07-30: answered our check2026-07-31: answered our check2026-08-01: answered our check2026-08-02: answered our check2026-08-03: answered our check2026-08-04: failed, unattributable2026-08-05: answered our check2026-08-06: answered our check2026-08-07: answered our check2026-08-08: answered our check2026-08-09: answered our check2026-08-10: answered our check2026-08-11: answered our check2026-08-12: answered our check2026-08-13: answered our check2026-08-14: answered our check2026-08-15: answered our check2026-08-16: answered our check2026-08-17: answered our check2026-08-18: answered our check2026-08-19: answered our check2026-08-20: answered our check2026-08-21: answered our check2026-08-22: answered our check2026-08-23: answered our check2026-08-24: answered our check2026-08-25: answered our check2026-08-26: answered our check2026-08-27: answered our check2026-08-28: answered our check2026-08-29: answered our check2026-08-30: answered our check2026-08-31: answered our check2026-09-01: answered our check2026-09-02: answered our check2026-09-03: answered our check2026-09-04: answered our check2026-09-05: answered our check2026-09-06: answered our check2026-09-07: answered our check2026-09-08: answered our check2026-09-09: answered our check2026-09-10: answered our check2026-09-11: answered our check2026-09-12: answered our check2026-09-13: answered our check
  • answered
  • host answered with an error
  • failed on our side
  • failed, unattributable

Every reading

The table the charts are drawn from. A missing day is missing from this table too — nothing is filled in.

DateScoreTierStatusOur check
2026-09-1363MediumUnknownup
2026-09-1263MediumUnknownup
2026-09-1163MediumUnknownup
2026-09-1063MediumUnknownup
2026-09-0963MediumUnknownup
2026-09-0863MediumUnknownup
2026-09-0763MediumUnknownup
2026-09-0663MediumUnknownup
2026-09-0563MediumUnknownup
2026-09-0463MediumUnknownup
2026-09-0363MediumUnknownup
2026-09-0263MediumUnknownup
2026-09-0163MediumUnknownup
2026-08-3161MediumUnknownup
2026-08-3061MediumUnknownup
2026-08-2961MediumUnknownup
2026-08-2861MediumUnknownup
2026-08-2761MediumUnknownup
2026-08-2661MediumUnknownup
2026-08-2561MediumUnknownup
2026-08-2461MediumUnknownup
2026-08-2361MediumUnknownup
2026-08-2261MediumUnknownup
2026-08-2161MediumUnknownup
2026-08-2061MediumUnknownup
2026-08-1961MediumUnknownup
2026-08-1861MediumUnknownup
2026-08-1761MediumUnknownup
2026-08-1661MediumUnknownup
2026-08-1561MediumUnknownup
2026-08-1461MediumUnknownup
2026-08-1361MediumUnknownup
2026-08-1261MediumUnknownup
2026-08-1161MediumUnknownup
2026-08-1061MediumUnknownup
2026-08-0961MediumUnknownup
2026-08-0861MediumUnknownup
2026-08-0761MediumUnknownup
2026-08-0661MediumUnknownup
2026-08-0561MediumUnknownup
2026-08-0439LowUnknownunknown
2026-08-0361MediumUnknownup
2026-08-0261MediumUnknownup
2026-08-0161MediumUnknownup
2026-07-3161MediumUnknownup
2026-07-3061MediumUnknownup
2026-07-2961MediumUnknownup
2026-07-2861MediumUnknownup
2026-07-2761MediumUnknownup
2026-07-2661MediumUnknownup
2026-07-2561MediumUnknownup
2026-07-2461MediumUnknownup
2026-07-2361MediumUnknownup
2026-07-2261MediumUnknownup
2026-07-2161MediumUnknownup
2026-07-2061MediumUnknownup
2026-07-1961MediumUnknownup
2026-07-1861MediumUnknownup
2026-07-1761MediumUnknownup
2026-07-1661MediumUnknownup
2026-07-1561MediumUnknownup
2026-07-1460MediumUnknownup

What happened alongside it

Releases, status changes, applied corrections and answered disputes, on the same dates — so a movement in the line can be read against an event rather than guessed at.

  1. Aug 5, 2026
    Sato Score tier: Low → Medium
    Score 39 → 61.
  2. Aug 4, 2026
    Sato Score tier: Medium → Low
    Score 61 → 39.
  3. Jul 14, 2026
    Edited: mcp endpoint url
  4. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  5. Jul 14, 2026
    Listed on Sato Hub
  6. Jul 14, 2026
    Sato Hub began tracking this listing

How to read this

  • · Every point is one UTC day. A day we did not capture is drawn as a gap, never joined across.
  • · A change on a marked methodology day is ours, not the project’s.
  • · The score says how open, active and verifiable the project is. It is not a safety, quality or returns grade.
  • · The inputs behind today’s score are published at /api/export/score-inputs.json and the arithmetic is reproducible on your own machine.
← Verification recordThis week’s moversDispute this score