Sato Hub
← Crypto.com AI Tools verification record

Score history

Crypto.com AI Tools

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

61

Change over 63d

-12

Days measured

63

Days missed

0

Sato Score, daily

2026-07-13 → 2026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (73 → 70). Not a change by the project.2026-07-15: Sato Hub changed the scoring method (70 → 71). Not a change by the project.2026-07-13: 73 (High)2026-07-14: 70 (High)2026-07-15: 71 (High)2026-07-16: 71 (High)2026-07-17: 71 (High)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: 61 (Medium)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: 71 (High)2026-08-12: 71 (High)2026-08-13: 71 (High)2026-08-14: 71 (High)2026-08-15: 71 (High)2026-08-16: 71 (High)2026-08-17: 71 (High)2026-08-18: 71 (High)2026-08-19: 71 (High)2026-08-20: 71 (High)2026-08-21: 71 (High)2026-08-22: 71 (High)2026-08-23: 71 (High)2026-08-24: 71 (High)2026-08-25: 71 (High)2026-08-26: 71 (High)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: 61 (Medium)2026-09-02: 61 (Medium)2026-09-03: 61 (Medium)2026-09-04: 61 (Medium)2026-09-05: 61 (Medium)2026-09-06: 61 (Medium)2026-09-07: 61 (Medium)2026-09-08: 61 (Medium)2026-09-09: 61 (Medium)2026-09-10: 61 (Medium)2026-09-11: 61 (Medium)2026-09-12: 61 (Medium)2026-09-13: 61 (Medium)73612026-07-132026-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

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

DateFromToChangeCause
2026-08-277161-10the project
2026-08-116171+10the project
2026-07-187161-10the project
2026-07-157071+1Sato Hub changed the scoring method
2026-07-147370-3Sato 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 & liveness25/35
35
Code transparency18/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification0/10
10

The observed record

8.1% 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: failed, unattributable2026-07-20: failed, unattributable2026-07-21: failed, unattributable2026-07-22: failed, unattributable2026-07-23: failed, unattributable2026-07-24: failed, unattributable2026-07-25: failed, unattributable2026-07-26: failed, unattributable2026-07-27: failed, unattributable2026-07-28: failed, unattributable2026-07-29: failed, unattributable2026-07-30: failed, unattributable2026-07-31: failed, unattributable2026-08-01: failed, unattributable2026-08-02: failed, unattributable2026-08-03: failed, unattributable2026-08-04: failed, unattributable2026-08-05: failed, unattributable2026-08-06: failed, unattributable2026-08-07: failed, unattributable2026-08-08: failed, unattributable2026-08-09: failed, unattributable2026-08-10: failed, unattributable2026-08-11: failed, unattributable2026-08-12: failed, unattributable2026-08-13: failed, unattributable2026-08-14: failed, unattributable2026-08-15: failed, unattributable2026-08-16: failed, unattributable2026-08-17: failed, unattributable2026-08-18: failed, unattributable2026-08-19: failed, unattributable2026-08-20: failed, unattributable2026-08-21: failed, unattributable2026-08-22: failed, unattributable2026-08-23: failed, unattributable2026-08-24: failed, unattributable2026-08-25: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-09-01: the host answered with an error2026-09-02: the host answered with an error2026-09-03: the host answered with an error2026-09-04: the host answered with an error2026-09-05: the host answered with an error2026-09-06: the host answered with an error2026-09-07: the host answered with an error2026-09-08: the host answered with an error2026-09-09: the host answered with an error2026-09-10: the host answered with an error2026-09-11: the host answered with an error2026-09-12: the host answered with an error2026-09-13: the host answered with an error
  • 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-1361MediumUnknowndown
2026-09-1261MediumUnknowndown
2026-09-1161MediumUnknowndown
2026-09-1061MediumUnknowndown
2026-09-0961MediumUnknowndown
2026-09-0861MediumUnknowndown
2026-09-0761MediumUnknowndown
2026-09-0661MediumUnknowndown
2026-09-0561MediumUnknowndown
2026-09-0461MediumUnknowndown
2026-09-0361MediumUnknowndown
2026-09-0261MediumUnknowndown
2026-09-0161MediumUnknowndown
2026-08-3161MediumUnknownunknown
2026-08-3061MediumUnknownunknown
2026-08-2961MediumUnknownunknown
2026-08-2861MediumUnknownunknown
2026-08-2761MediumUnknownunknown
2026-08-2671HighUnknownunknown
2026-08-2571HighUnknownunknown
2026-08-2471HighUnknownunknown
2026-08-2371HighUnknownunknown
2026-08-2271HighUnknownunknown
2026-08-2171HighUnknownunknown
2026-08-2071HighUnknownunknown
2026-08-1971HighUnknownunknown
2026-08-1871HighUnknownunknown
2026-08-1771HighUnknownunknown
2026-08-1671HighUnknownunknown
2026-08-1571HighUnknownunknown
2026-08-1471HighUnknownunknown
2026-08-1371HighUnknownunknown
2026-08-1271HighUnknownunknown
2026-08-1171HighUnknownunknown
2026-08-1061MediumUnknownunknown
2026-08-0961MediumUnknownunknown
2026-08-0861MediumUnknownunknown
2026-08-0761MediumUnknownunknown
2026-08-0661MediumUnknownunknown
2026-08-0561MediumUnknownunknown
2026-08-0461MediumUnknownunknown
2026-08-0361MediumUnknownunknown
2026-08-0261MediumUnknownunknown
2026-08-0161MediumUnknownunknown
2026-07-3161MediumUnknownunknown
2026-07-3061MediumUnknownunknown
2026-07-2961MediumUnknownunknown
2026-07-2861MediumUnknownunknown
2026-07-2761MediumUnknownunknown
2026-07-2661MediumUnknownunknown
2026-07-2561MediumUnknownunknown
2026-07-2461MediumUnknownunknown
2026-07-2361MediumUnknownunknown
2026-07-2261MediumUnknownunknown
2026-07-2161MediumUnknownunknown
2026-07-2061MediumUnknownunknown
2026-07-1961MediumUnknownunknown
2026-07-1861MediumUnknownup
2026-07-1771HighUnknownup
2026-07-1671HighUnknownup
2026-07-1571HighUnknownup
2026-07-1470HighUnknownup
2026-07-1373HighUnknownnot checked

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 27, 2026
    Sato Score tier: High → Medium
    Score 71 → 61.
  2. Aug 11, 2026
    Sato Score tier: Medium → High
    Score 61 → 71.
  3. Jul 20, 2026
    Edited: mcp endpoint url
  4. Jul 19, 2026
    Edited: mcp endpoint url
  5. Jul 18, 2026
    Sato Score tier: High → Medium
    Score 71 → 61.
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 13, 2026
    Listed on Sato Hub
  8. Jul 13, 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