Sato Hub
← SQD Portal MCP verification record

Score history

SQD Portal 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

61

Change over 57d

+5

Days measured

57

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-015861+3Sato Hub changed the scoring method
2026-08-274758+11the project
2026-07-265747-10the project
2026-07-205657+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 & liveness35/35
35
Code transparency17/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-1361MediumActiveup
2026-09-1261MediumActiveup
2026-09-1161MediumActiveup
2026-09-1061MediumActiveup
2026-09-0961MediumActiveup
2026-09-0861MediumActiveup
2026-09-0761MediumActiveup
2026-09-0661MediumActiveup
2026-09-0561MediumActiveup
2026-09-0461MediumActiveup
2026-09-0361MediumActiveup
2026-09-0261MediumActiveup
2026-09-0161MediumActiveup
2026-08-3158MediumActiveup
2026-08-3058MediumActiveup
2026-08-2958MediumActiveup
2026-08-2858MediumActiveup
2026-08-2758MediumActiveup
2026-08-2647MediumActiveup
2026-08-2547MediumActiveup
2026-08-2447MediumActiveup
2026-08-2347MediumActiveup
2026-08-2247MediumActiveup
2026-08-2147MediumActiveup
2026-08-2047MediumActiveup
2026-08-1947MediumActiveup
2026-08-1847MediumActiveup
2026-08-1747MediumActiveup
2026-08-1647MediumActiveup
2026-08-1547MediumActiveup
2026-08-1447MediumActiveup
2026-08-1347MediumActiveup
2026-08-1247MediumActiveup
2026-08-1147MediumActiveup
2026-08-1047MediumActiveup
2026-08-0947MediumActiveup
2026-08-0847MediumActiveup
2026-08-0747MediumActiveup
2026-08-0647MediumActiveup
2026-08-0547MediumActiveup
2026-08-0447MediumActiveup
2026-08-0347MediumActiveup
2026-08-0247MediumActiveup
2026-08-0147MediumActiveup
2026-07-3147MediumActiveup
2026-07-3047MediumActiveup
2026-07-2947MediumActiveup
2026-07-2847MediumActiveup
2026-07-2747MediumActiveup
2026-07-2647MediumActiveup
2026-07-2557MediumActiveup
2026-07-2457MediumActiveup
2026-07-2357MediumActiveup
2026-07-2257MediumActiveup
2026-07-2157MediumActiveup
2026-07-2057MediumActiveup
2026-07-1956MediumActiveup

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 7, 2026
    New release published
  2. Sep 5, 2026
    New release published
  3. Aug 27, 2026
    5 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  4. Jul 20, 2026
    Edited: deploy spec
  5. Jul 19, 2026
    Listed on Sato Hub
  6. 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