Sato Hub
go-sui-mcp verification record

Score history

go-sui-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

60

Change over 62d

+1

Days measured

62

Days missed

0

Sato Score, daily

2026-07-142026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (59 → 60). Not a change by the project.2026-07-14: 59 (Medium)2026-07-15: 59 (Medium)2026-07-16: 59 (Medium)2026-07-17: 59 (Medium)2026-07-18: 59 (Medium)2026-07-19: 59 (Medium)2026-07-20: 60 (Medium)2026-07-21: 60 (Medium)2026-07-22: 60 (Medium)2026-07-23: 60 (Medium)2026-07-24: 60 (Medium)2026-07-25: 60 (Medium)2026-07-26: 60 (Medium)2026-07-27: 60 (Medium)2026-07-28: 70 (High)2026-07-29: 70 (High)2026-07-30: 70 (High)2026-07-31: 70 (High)2026-08-01: 70 (High)2026-08-02: 70 (High)2026-08-03: 70 (High)2026-08-04: 70 (High)2026-08-05: 70 (High)2026-08-06: 70 (High)2026-08-07: 70 (High)2026-08-08: 70 (High)2026-08-09: 70 (High)2026-08-10: 70 (High)2026-08-11: 70 (High)2026-08-12: 70 (High)2026-08-13: 70 (High)2026-08-14: 70 (High)2026-08-15: 70 (High)2026-08-16: 70 (High)2026-08-17: 70 (High)2026-08-18: 70 (High)2026-08-19: 70 (High)2026-08-20: 70 (High)2026-08-21: 70 (High)2026-08-22: 60 (Medium)2026-08-23: 60 (Medium)2026-08-24: 60 (Medium)2026-08-25: 60 (Medium)2026-08-26: 60 (Medium)2026-08-27: 60 (Medium)2026-08-28: 60 (Medium)2026-08-29: 60 (Medium)2026-08-30: 60 (Medium)2026-08-31: 60 (Medium)2026-09-01: 60 (Medium)2026-09-02: 60 (Medium)2026-09-03: 60 (Medium)2026-09-04: 60 (Medium)2026-09-05: 60 (Medium)2026-09-06: 60 (Medium)2026-09-07: 60 (Medium)2026-09-08: 60 (Medium)2026-09-09: 60 (Medium)2026-09-10: 60 (Medium)2026-09-11: 60 (Medium)2026-09-12: 60 (Medium)2026-09-13: 60 (Medium)5970602026-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, 1 caused by a revision of the scoring method.

DateFromToChangeCause
2026-08-227060-10the project
2026-07-286070+10the project
2026-07-205960+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 & liveness25/35
35
Code transparency17/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification0/10
10

The observed record

35.5% 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: answered our check2026-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-1360MediumActivedown
2026-09-1260MediumActivedown
2026-09-1160MediumActivedown
2026-09-1060MediumActivedown
2026-09-0960MediumActivedown
2026-09-0860MediumActivedown
2026-09-0760MediumActivedown
2026-09-0660MediumActivedown
2026-09-0560MediumActivedown
2026-09-0460MediumActivedown
2026-09-0360MediumActivedown
2026-09-0260MediumActivedown
2026-09-0160MediumActivedown
2026-08-3160MediumActiveunknown
2026-08-3060MediumActiveunknown
2026-08-2960MediumActiveunknown
2026-08-2860MediumActiveunknown
2026-08-2760MediumActiveunknown
2026-08-2660MediumActiveunknown
2026-08-2560MediumActiveunknown
2026-08-2460MediumActiveunknown
2026-08-2360MediumActiveunknown
2026-08-2260MediumActiveunknown
2026-08-2170HighActiveunknown
2026-08-2070HighActiveunknown
2026-08-1970HighActiveunknown
2026-08-1870HighActiveunknown
2026-08-1770HighActiveunknown
2026-08-1670HighActiveunknown
2026-08-1570HighActiveunknown
2026-08-1470HighActiveunknown
2026-08-1370HighActiveunknown
2026-08-1270HighActiveunknown
2026-08-1170HighActiveunknown
2026-08-1070HighActiveunknown
2026-08-0970HighActiveunknown
2026-08-0870HighActiveunknown
2026-08-0770HighActiveunknown
2026-08-0670HighActiveunknown
2026-08-0570HighActiveunknown
2026-08-0470HighActiveup
2026-08-0370HighActiveup
2026-08-0270HighActiveup
2026-08-0170HighActiveup
2026-07-3170HighActiveup
2026-07-3070HighActiveup
2026-07-2970HighActiveup
2026-07-2870HighActiveup
2026-07-2760MediumActiveup
2026-07-2660MediumActiveup
2026-07-2560MediumActiveup
2026-07-2460MediumActiveup
2026-07-2360MediumActiveup
2026-07-2260MediumActiveup
2026-07-2160MediumActiveup
2026-07-2060MediumActiveup
2026-07-1959MediumActiveup
2026-07-1859MediumActiveup
2026-07-1759MediumActiveup
2026-07-1659MediumActiveup
2026-07-1559MediumActiveup
2026-07-1459MediumActiveup

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 22, 2026
    Sato Score tier: High → Medium
    Score 70 → 60.
  2. Jul 28, 2026
    Sato Score tier: Medium → High
    Score 60 → 70.
  3. Jul 20, 2026
    Edited: deploy spec
  4. Jul 14, 2026
    Enriched: deployment options, supported integrations
  5. Jul 14, 2026
    Auto-enriched: creator profile url
  6. Jul 14, 2026
    Listed on Sato Hub
  7. 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.