Sato Hub
← SODAX Builders MCP verification record

Score history

SODAX Builders 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

79

Change over 57d

+15

Days measured

57

Days missed

0

Sato Score, daily

2026-07-19 → 2026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (64 → 75). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (76 → 79). Not a change by the project.2026-07-19: 64 (Medium)2026-07-20: 75 (High)2026-07-21: 76 (High)2026-07-22: 76 (High)2026-07-23: 76 (High)2026-07-24: 76 (High)2026-07-25: 76 (High)2026-07-26: 76 (High)2026-07-27: 76 (High)2026-07-28: 76 (High)2026-07-29: 76 (High)2026-07-30: 76 (High)2026-07-31: 76 (High)2026-08-01: 76 (High)2026-08-02: 76 (High)2026-08-03: 76 (High)2026-08-04: 76 (High)2026-08-05: 76 (High)2026-08-06: 76 (High)2026-08-07: 76 (High)2026-08-08: 76 (High)2026-08-09: 76 (High)2026-08-10: 76 (High)2026-08-11: 76 (High)2026-08-12: 76 (High)2026-08-13: 76 (High)2026-08-14: 76 (High)2026-08-15: 76 (High)2026-08-16: 76 (High)2026-08-17: 76 (High)2026-08-18: 76 (High)2026-08-19: 76 (High)2026-08-20: 76 (High)2026-08-21: 76 (High)2026-08-22: 76 (High)2026-08-23: 76 (High)2026-08-24: 76 (High)2026-08-25: 76 (High)2026-08-26: 76 (High)2026-08-27: 76 (High)2026-08-28: 76 (High)2026-08-29: 76 (High)2026-08-30: 76 (High)2026-08-31: 76 (High)2026-09-01: 79 (High)2026-09-02: 79 (High)2026-09-03: 79 (High)2026-09-04: 79 (High)2026-09-05: 79 (High)2026-09-06: 79 (High)2026-09-07: 79 (High)2026-09-08: 79 (High)2026-09-09: 79 (High)2026-09-10: 79 (High)2026-09-11: 79 (High)2026-09-12: 79 (High)2026-09-13: 79 (High)6479792026-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-017679+3Sato Hub changed the scoring method
2026-07-217576+1the project
2026-07-206475+11Sato 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 & liveness35/35
35
Code transparency17/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance8/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-1379HighActiveup
2026-09-1279HighActiveup
2026-09-1179HighActiveup
2026-09-1079HighActiveup
2026-09-0979HighActiveup
2026-09-0879HighActiveup
2026-09-0779HighActiveup
2026-09-0679HighActiveup
2026-09-0579HighActiveup
2026-09-0479HighActiveup
2026-09-0379HighActiveup
2026-09-0279HighActiveup
2026-09-0179HighActiveup
2026-08-3176HighActiveup
2026-08-3076HighActiveup
2026-08-2976HighActiveup
2026-08-2876HighActiveup
2026-08-2776HighActiveup
2026-08-2676HighActiveup
2026-08-2576HighActiveup
2026-08-2476HighActiveup
2026-08-2376HighActiveup
2026-08-2276HighActiveup
2026-08-2176HighActiveup
2026-08-2076HighActiveup
2026-08-1976HighActiveup
2026-08-1876HighActiveup
2026-08-1776HighActiveup
2026-08-1676HighActiveup
2026-08-1576HighActiveup
2026-08-1476HighActiveup
2026-08-1376HighActiveup
2026-08-1276HighActiveup
2026-08-1176HighActiveup
2026-08-1076HighActiveup
2026-08-0976HighActiveup
2026-08-0876HighActiveup
2026-08-0776HighActiveup
2026-08-0676HighActiveup
2026-08-0576HighActiveup
2026-08-0476HighActiveup
2026-08-0376HighActiveup
2026-08-0276HighActiveup
2026-08-0176HighActiveup
2026-07-3176HighActiveup
2026-07-3076HighActiveup
2026-07-2976HighActiveup
2026-07-2876HighActiveup
2026-07-2776HighActiveup
2026-07-2676HighActiveup
2026-07-2576HighActiveup
2026-07-2476HighActiveup
2026-07-2376HighActiveup
2026-07-2276HighActiveup
2026-07-2176HighActiveup
2026-07-2075HighActiveup
2026-07-1964MediumActiveup

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 3, 2026
    New release published
  2. Jul 20, 2026
    Edited: mcp endpoint url
  3. Jul 20, 2026
    Sato Score tier: Medium → High
    Score 64 → 75.
  4. Jul 20, 2026
    Edited: deploy spec
  5. Jul 19, 2026
    Edited: description long
  6. Jul 19, 2026
    Listed on Sato Hub
  7. 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.
← Verification recordThis week’s moversDispute this score