Sato Hub
Messari MCP verification record

Score history

Messari 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

28

Change over 63d

+6

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-07-202428+4Sato Hub changed the scoring method
2026-07-142224+2Sato 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 & liveness8/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance10/15
15
Independent verification4/10
10

The observed record

0% 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: failed, unattributable2026-07-15: failed, unattributable2026-07-16: failed, unattributable2026-07-17: failed, unattributable2026-07-18: failed, unattributable2026-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-1328LowActivedown
2026-09-1228LowActivedown
2026-09-1128LowActivedown
2026-09-1028LowActivedown
2026-09-0928LowActivedown
2026-09-0828LowActivedown
2026-09-0728LowActivedown
2026-09-0628LowActivedown
2026-09-0528LowActivedown
2026-09-0428LowActivedown
2026-09-0328LowActivedown
2026-09-0228LowActivedown
2026-09-0128LowActivedown
2026-08-3128LowActiveunknown
2026-08-3028LowActiveunknown
2026-08-2928LowActiveunknown
2026-08-2828LowActiveunknown
2026-08-2728LowActiveunknown
2026-08-2628LowActiveunknown
2026-08-2528LowActiveunknown
2026-08-2428LowActiveunknown
2026-08-2328LowActiveunknown
2026-08-2228LowActiveunknown
2026-08-2128LowActiveunknown
2026-08-2028LowActiveunknown
2026-08-1928LowActiveunknown
2026-08-1828LowActiveunknown
2026-08-1728LowActiveunknown
2026-08-1628LowActiveunknown
2026-08-1528LowActiveunknown
2026-08-1428LowActiveunknown
2026-08-1328LowActiveunknown
2026-08-1228LowActiveunknown
2026-08-1128LowActiveunknown
2026-08-1028LowActiveunknown
2026-08-0928LowActiveunknown
2026-08-0828LowActiveunknown
2026-08-0728LowActiveunknown
2026-08-0628LowActiveunknown
2026-08-0528LowActiveunknown
2026-08-0428LowActiveunknown
2026-08-0328LowActiveunknown
2026-08-0228LowActiveunknown
2026-08-0128LowActiveunknown
2026-07-3128LowActiveunknown
2026-07-3028LowActiveunknown
2026-07-2928LowActiveunknown
2026-07-2828LowActiveunknown
2026-07-2728LowActiveunknown
2026-07-2628LowActiveunknown
2026-07-2528LowActiveunknown
2026-07-2428LowActiveunknown
2026-07-2328LowActiveunknown
2026-07-2228LowActiveunknown
2026-07-2128LowActiveunknown
2026-07-2028LowActiveunknown
2026-07-1924LowActiveunknown
2026-07-1824LowActiveunknown
2026-07-1724LowActiveunknown
2026-07-1624LowActiveunknown
2026-07-1524LowActiveunknown
2026-07-1424LowActiveunknown
2026-07-1322LowActivenot 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. Jul 20, 2026
    Edited: mcp endpoint url
  2. Jul 19, 2026
    Edited: mcp endpoint url
  3. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  4. Jul 13, 2026
    Listed on Sato Hub
  5. 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.