Sato Hub
← Deside MCP verification record

Score history

Deside 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

65

Change over 57d

+24

Days measured

57

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-08-175565+10the project
2026-08-046555-10the project
2026-07-213865+27the project
2026-07-204138-3Sato 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 transparency16/20
20
Interface verifiability8/10
10
Docs & demo0/10
10
Listing transparency & provenance6/15
15
Independent verification0/10
10

The observed record

1.8% 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: 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-1365MediumActivedown
2026-09-1265MediumActivedown
2026-09-1165MediumActivedown
2026-09-1065MediumActivedown
2026-09-0965MediumActivedown
2026-09-0865MediumActivedown
2026-09-0765MediumActivedown
2026-09-0665MediumActivedown
2026-09-0565MediumActivedown
2026-09-0465MediumActivedown
2026-09-0365MediumActivedown
2026-09-0265MediumActivedown
2026-09-0165MediumActivedown
2026-08-3165MediumActiveunknown
2026-08-3065MediumActiveunknown
2026-08-2965MediumActiveunknown
2026-08-2865MediumActiveunknown
2026-08-2765MediumActiveunknown
2026-08-2665MediumActiveunknown
2026-08-2565MediumActiveunknown
2026-08-2465MediumActiveunknown
2026-08-2365MediumActiveunknown
2026-08-2265MediumActiveunknown
2026-08-2165MediumActiveunknown
2026-08-2065MediumActiveunknown
2026-08-1965MediumActiveunknown
2026-08-1865MediumActiveunknown
2026-08-1765MediumActiveunknown
2026-08-1655MediumActiveunknown
2026-08-1555MediumActiveunknown
2026-08-1455MediumActiveunknown
2026-08-1355MediumActiveunknown
2026-08-1255MediumActiveunknown
2026-08-1155MediumActiveunknown
2026-08-1055MediumActiveunknown
2026-08-0955MediumActiveunknown
2026-08-0855MediumActiveunknown
2026-08-0755MediumActiveunknown
2026-08-0655MediumActiveunknown
2026-08-0555MediumActiveunknown
2026-08-0455MediumActiveunknown
2026-08-0365MediumActiveunknown
2026-08-0265MediumActiveunknown
2026-08-0165MediumActiveunknown
2026-07-3165MediumActiveunknown
2026-07-3065MediumActiveunknown
2026-07-2965MediumActiveunknown
2026-07-2865MediumActiveunknown
2026-07-2765MediumActiveunknown
2026-07-2665MediumActiveunknown
2026-07-2565MediumActiveunknown
2026-07-2465MediumActiveunknown
2026-07-2365MediumActiveunknown
2026-07-2265MediumActiveunknown
2026-07-2165MediumActiveunknown
2026-07-2038LowActiveunknown
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 21, 2026
    Sato Score tier: Low → Medium
    Score 38 → 65.
  2. Jul 21, 2026
    Verified: deploy spec
  3. Jul 20, 2026
    Edited: mcp endpoint url
  4. Jul 20, 2026
    Sato Score tier: Medium → Low
    Score 41 → 38.
  5. Jul 19, 2026
    Edited: github url, website url
  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