Sato Hub
CryptoIZ MCP verification record

Score history

CryptoIZ MCP

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

45

Change over 57d

-1

Days measured

57

Days missed

0

Sato Score, daily

2026-07-192026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (46 → 47). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (43 → 46). Not a change by the project.2026-07-19: 46 (Medium)2026-07-20: 47 (Medium)2026-07-21: 47 (Medium)2026-07-22: 47 (Medium)2026-07-23: 47 (Medium)2026-07-24: 47 (Medium)2026-07-25: 47 (Medium)2026-07-26: 42 (Medium)2026-07-27: 42 (Medium)2026-07-28: 42 (Medium)2026-07-29: 42 (Medium)2026-07-30: 42 (Medium)2026-07-31: 42 (Medium)2026-08-01: 42 (Medium)2026-08-02: 42 (Medium)2026-08-03: 42 (Medium)2026-08-04: 42 (Medium)2026-08-05: 42 (Medium)2026-08-06: 42 (Medium)2026-08-07: 42 (Medium)2026-08-08: 42 (Medium)2026-08-09: 42 (Medium)2026-08-10: 42 (Medium)2026-08-11: 42 (Medium)2026-08-12: 42 (Medium)2026-08-13: 42 (Medium)2026-08-14: 42 (Medium)2026-08-15: 42 (Medium)2026-08-16: 42 (Medium)2026-08-17: 42 (Medium)2026-08-18: 42 (Medium)2026-08-19: 42 (Medium)2026-08-20: 42 (Medium)2026-08-21: 42 (Medium)2026-08-22: 42 (Medium)2026-08-23: 42 (Medium)2026-08-24: 42 (Medium)2026-08-25: 42 (Medium)2026-08-26: 42 (Medium)2026-08-27: 43 (Medium)2026-08-28: 43 (Medium)2026-08-29: 43 (Medium)2026-08-30: 43 (Medium)2026-08-31: 43 (Medium)2026-09-01: 46 (Medium)2026-09-02: 46 (Medium)2026-09-03: 46 (Medium)2026-09-04: 46 (Medium)2026-09-05: 46 (Medium)2026-09-06: 46 (Medium)2026-09-07: 46 (Medium)2026-09-08: 39 (Low)2026-09-09: 45 (Medium)2026-09-10: 45 (Medium)2026-09-11: 45 (Medium)2026-09-12: 45 (Medium)2026-09-13: 45 (Medium)4647452026-07-192026-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

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

DateFromToChangeCause
2026-09-093945+6the project
2026-09-084639-7the project
2026-09-014346+3Sato Hub changed the scoring method
2026-08-274243+1the project
2026-07-264742-5the project
2026-07-204647+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 & liveness20/35
35
Code transparency17/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance6/15
15
Independent verification2/10
10

The observed record

98.2% of Sato Hub's own daily checks succeeded over 57 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-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: answered our check2026-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: failed on our side — not attributable to the project2026-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-1345MediumActiveup
2026-09-1245MediumActiveup
2026-09-1145MediumActiveup
2026-09-1045MediumActiveup
2026-09-0945MediumActiveup
2026-09-0839LowActiveinconclusive
2026-09-0746MediumActiveup
2026-09-0646MediumActiveup
2026-09-0546MediumActiveup
2026-09-0446MediumActiveup
2026-09-0346MediumActiveup
2026-09-0246MediumActiveup
2026-09-0146MediumActiveup
2026-08-3143MediumActiveup
2026-08-3043MediumActiveup
2026-08-2943MediumActiveup
2026-08-2843MediumActiveup
2026-08-2743MediumActiveup
2026-08-2642MediumActiveup
2026-08-2542MediumActiveup
2026-08-2442MediumActiveup
2026-08-2342MediumActiveup
2026-08-2242MediumActiveup
2026-08-2142MediumActiveup
2026-08-2042MediumActiveup
2026-08-1942MediumActiveup
2026-08-1842MediumActiveup
2026-08-1742MediumActiveup
2026-08-1642MediumActiveup
2026-08-1542MediumActiveup
2026-08-1442MediumActiveup
2026-08-1342MediumActiveup
2026-08-1242MediumActiveup
2026-08-1142MediumActiveup
2026-08-1042MediumActiveup
2026-08-0942MediumActiveup
2026-08-0842MediumActiveup
2026-08-0742MediumActiveup
2026-08-0642MediumActiveup
2026-08-0542MediumActiveup
2026-08-0442MediumActiveup
2026-08-0342MediumActiveup
2026-08-0242MediumActiveup
2026-08-0142MediumActiveup
2026-07-3142MediumActiveup
2026-07-3042MediumActiveup
2026-07-2942MediumActiveup
2026-07-2842MediumActiveup
2026-07-2742MediumActiveup
2026-07-2642MediumActiveup
2026-07-2547MediumActiveup
2026-07-2447MediumActiveup
2026-07-2347MediumActiveup
2026-07-2247MediumActiveup
2026-07-2147MediumActiveup
2026-07-2047MediumActiveup
2026-07-1946MediumActiveup

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. Sep 9, 2026
    Sato Score tier: Low → Medium
    Score 39 → 45.
  2. Sep 8, 2026
    Sato Score tier: Medium → Low
    Score 46 → 39.
  3. Jul 20, 2026
    Edited: deploy spec
  4. Jul 19, 2026
    Listed on Sato Hub
  5. Jul 19, 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.