Sato Hub
Cryo MCP Server verification record

Score history

Cryo MCP Server

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

47

Change over 57d

+6

Days measured

57

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-014447+3Sato Hub changed the scoring method
2026-07-214244+2the project
2026-07-204142+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 transparency18/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance6/15
15
Independent verification3/10
10

The observed record

100% 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: 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-1347MediumActiveup
2026-09-1247MediumActiveup
2026-09-1147MediumActiveup
2026-09-1047MediumActiveup
2026-09-0947MediumActiveup
2026-09-0847MediumActiveup
2026-09-0747MediumActiveup
2026-09-0647MediumActiveup
2026-09-0547MediumActiveup
2026-09-0447MediumActiveup
2026-09-0347MediumActiveup
2026-09-0247MediumActiveup
2026-09-0147MediumActiveup
2026-08-3144MediumActiveup
2026-08-3044MediumActiveup
2026-08-2944MediumActiveup
2026-08-2844MediumActiveup
2026-08-2744MediumActiveup
2026-08-2644MediumActiveup
2026-08-2544MediumActiveup
2026-08-2444MediumActiveup
2026-08-2344MediumActiveup
2026-08-2244MediumActiveup
2026-08-2144MediumActiveup
2026-08-2044MediumActiveup
2026-08-1944MediumActiveup
2026-08-1844MediumActiveup
2026-08-1744MediumActiveup
2026-08-1644MediumActiveup
2026-08-1544MediumActiveup
2026-08-1444MediumActiveup
2026-08-1344MediumActiveup
2026-08-1244MediumActiveup
2026-08-1144MediumActiveup
2026-08-1044MediumActiveup
2026-08-0944MediumActiveup
2026-08-0844MediumActiveup
2026-08-0744MediumActiveup
2026-08-0644MediumActiveup
2026-08-0544MediumActiveup
2026-08-0444MediumActiveup
2026-08-0344MediumActiveup
2026-08-0244MediumActiveup
2026-08-0144MediumActiveup
2026-07-3144MediumActiveup
2026-07-3044MediumActiveup
2026-07-2944MediumActiveup
2026-07-2844MediumActiveup
2026-07-2744MediumActiveup
2026-07-2644MediumActiveup
2026-07-2544MediumActiveup
2026-07-2444MediumActiveup
2026-07-2344MediumActiveup
2026-07-2244MediumActiveup
2026-07-2144MediumActiveup
2026-07-2042MediumActiveup
2026-07-1941MediumActiveup

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. Jul 20, 2026
    Edited: deploy spec
  2. Jul 19, 2026
    Listed on Sato Hub
  3. 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.