Sato Hub
Score history

OpenDexter

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

26

Change over 103d

-11

Days measured

103

Days missed

0

Sato Score, daily

2026-07-19 → 2026-10-29
02550751002026-07-20: Sato Hub changed the scoring method (37 → 53). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (53 → 29). Not a change by the project.2026-07-19: 37 (Low)2026-07-20: 53 (Medium)2026-07-21: 53 (Medium)2026-07-22: 53 (Medium)2026-07-23: 53 (Medium)2026-07-24: 53 (Medium)2026-07-25: 53 (Medium)2026-07-26: 53 (Medium)2026-07-27: 53 (Medium)2026-07-28: 53 (Medium)2026-07-29: 53 (Medium)2026-07-30: 53 (Medium)2026-07-31: 53 (Medium)2026-08-01: 53 (Medium)2026-08-02: 53 (Medium)2026-08-03: 53 (Medium)2026-08-04: 53 (Medium)2026-08-05: 53 (Medium)2026-08-06: 53 (Medium)2026-08-07: 53 (Medium)2026-08-08: 53 (Medium)2026-08-09: 53 (Medium)2026-08-10: 53 (Medium)2026-08-11: 53 (Medium)2026-08-12: 53 (Medium)2026-08-13: 53 (Medium)2026-08-14: 53 (Medium)2026-08-15: 53 (Medium)2026-08-16: 53 (Medium)2026-08-17: 53 (Medium)2026-08-18: 53 (Medium)2026-08-19: 53 (Medium)2026-08-20: 53 (Medium)2026-08-21: 53 (Medium)2026-08-22: 53 (Medium)2026-08-23: 53 (Medium)2026-08-24: 53 (Medium)2026-08-25: 53 (Medium)2026-08-26: 53 (Medium)2026-08-27: 53 (Medium)2026-08-28: 53 (Medium)2026-08-29: 53 (Medium)2026-08-30: 53 (Medium)2026-08-31: 53 (Medium)2026-09-01: 29 (Low)2026-09-02: 28 (Low)2026-09-03: 28 (Low)2026-09-04: 26 (Low)2026-09-05: 26 (Low)2026-09-06: 26 (Low)2026-09-07: 26 (Low)2026-09-08: 26 (Low)2026-09-09: 26 (Low)2026-09-10: 26 (Low)2026-09-11: 26 (Low)2026-09-12: 26 (Low)2026-09-13: 26 (Low)2026-09-14: 26 (Low)2026-09-15: 26 (Low)2026-09-16: 26 (Low)2026-09-17: 26 (Low)2026-09-18: 26 (Low)2026-09-19: 26 (Low)2026-09-20: 26 (Low)2026-09-21: 26 (Low)2026-09-22: 26 (Low)2026-09-23: 26 (Low)2026-09-24: 26 (Low)2026-09-25: 26 (Low)2026-09-26: 26 (Low)2026-09-27: 26 (Low)2026-09-28: 26 (Low)2026-09-29: 26 (Low)2026-09-30: 26 (Low)2026-10-01: 26 (Low)2026-10-02: 26 (Low)2026-10-03: 26 (Low)2026-10-04: 26 (Low)2026-10-05: 26 (Low)2026-10-06: 26 (Low)2026-10-07: 26 (Low)2026-10-08: 26 (Low)2026-10-09: 26 (Low)2026-10-10: 26 (Low)2026-10-11: 26 (Low)2026-10-12: 26 (Low)2026-10-13: 26 (Low)2026-10-14: 26 (Low)2026-10-15: 26 (Low)2026-10-16: 26 (Low)2026-10-17: 26 (Low)2026-10-18: 26 (Low)2026-10-19: 26 (Low)2026-10-20: 26 (Low)2026-10-21: 26 (Low)2026-10-22: 26 (Low)2026-10-23: 26 (Low)2026-10-24: 26 (Low)2026-10-25: 26 (Low)2026-10-26: 26 (Low)2026-10-27: 26 (Low)2026-10-28: 26 (Low)2026-10-29: 26 (Low)3753262026-07-192026-10-29

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-042826-2the project
2026-09-022928-1the project
2026-09-015329-24Sato Hub changed the scoring method
2026-07-203753+16Sato 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 transparency12/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance6/15
15
Independent verification0/10
10

The observed record

42.7% of 103 daily checks since 2026-07-19 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

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: 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: failed on our side — not attributable to the project2026-09-12: the host answered with an error2026-09-13: the host answered with an error2026-09-14: the host answered with an error2026-09-15: the host answered with an error2026-09-16: the host answered with an error2026-09-17: the host answered with an error2026-09-18: the host answered with an error2026-09-19: the host answered with an error2026-09-20: the host answered with an error2026-09-21: the host answered with an error2026-09-22: the host answered with an error2026-09-23: failed on our side — not attributable to the project2026-09-24: failed on our side — not attributable to the project2026-09-25: failed on our side — not attributable to the project2026-09-26: failed on our side — not attributable to the project2026-09-27: failed on our side — not attributable to the project2026-09-28: failed on our side — not attributable to the project2026-09-29: failed on our side — not attributable to the project2026-09-30: failed on our side — not attributable to the project2026-10-01: failed on our side — not attributable to the project2026-10-02: failed on our side — not attributable to the project2026-10-03: failed on our side — not attributable to the project2026-10-04: failed on our side — not attributable to the project2026-10-05: failed on our side — not attributable to the project2026-10-06: failed on our side — not attributable to the project2026-10-07: failed on our side — not attributable to the project2026-10-08: failed on our side — not attributable to the project2026-10-09: failed on our side — not attributable to the project2026-10-10: failed on our side — not attributable to the project2026-10-11: failed on our side — not attributable to the project2026-10-12: failed on our side — not attributable to the project2026-10-13: failed on our side — not attributable to the project2026-10-14: failed on our side — not attributable to the project2026-10-15: failed on our side — not attributable to the project2026-10-16: failed on our side — not attributable to the project2026-10-17: failed on our side — not attributable to the project2026-10-18: failed on our side — not attributable to the project2026-10-19: the host answered with an error2026-10-20: failed on our side — not attributable to the project2026-10-21: failed on our side — not attributable to the project2026-10-22: failed on our side — not attributable to the project2026-10-23: failed on our side — not attributable to the project2026-10-24: failed on our side — not attributable to the project2026-10-25: failed on our side — not attributable to the project2026-10-26: failed on our side — not attributable to the project2026-10-27: failed on our side — not attributable to the project2026-10-28: failed on our side — not attributable to the project2026-10-29: failed on our side — not attributable to the project
  • 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-10-2926LowActiveinconclusive
2026-10-2826LowActiveinconclusive
2026-10-2726LowActiveinconclusive
2026-10-2626LowActiveinconclusive
2026-10-2526LowActiveinconclusive
2026-10-2426LowActiveinconclusive
2026-10-2326LowActiveinconclusive
2026-10-2226LowActiveinconclusive
2026-10-2126LowActiveinconclusive
2026-10-2026LowActiveinconclusive
2026-10-1926LowActivedown
2026-10-1826LowActiveinconclusive
2026-10-1726LowActiveinconclusive
2026-10-1626LowActiveinconclusive
2026-10-1526LowActiveinconclusive
2026-10-1426LowActiveinconclusive
2026-10-1326LowActiveinconclusive
2026-10-1226LowActiveinconclusive
2026-10-1126LowActiveinconclusive
2026-10-1026LowActiveinconclusive
2026-10-0926LowActiveinconclusive
2026-10-0826LowActiveinconclusive
2026-10-0726LowActiveinconclusive
2026-10-0626LowActiveinconclusive
2026-10-0526LowActiveinconclusive
2026-10-0426LowActiveinconclusive
2026-10-0326LowActiveinconclusive
2026-10-0226LowActiveinconclusive
2026-10-0126LowActiveinconclusive
2026-09-3026LowActiveinconclusive
2026-09-2926LowActiveinconclusive
2026-09-2826LowActiveinconclusive
2026-09-2726LowActiveinconclusive
2026-09-2626LowActiveinconclusive
2026-09-2526LowActiveinconclusive
2026-09-2426LowActiveinconclusive
2026-09-2326LowActiveinconclusive
2026-09-2226LowActivedown
2026-09-2126LowActivedown
2026-09-2026LowActivedown
2026-09-1926LowActivedown
2026-09-1826LowActivedown
2026-09-1726LowActivedown
2026-09-1626LowActivedown
2026-09-1526LowActivedown
2026-09-1426LowActivedown
2026-09-1326LowActivedown
2026-09-1226LowActivedown
2026-09-1126LowActiveinconclusive
2026-09-1026LowActivedown
2026-09-0926LowActivedown
2026-09-0826LowActivedown
2026-09-0726LowActivedown
2026-09-0626LowActivedown
2026-09-0526LowActivedown
2026-09-0426LowActivedown
2026-09-0328LowActivedown
2026-09-0228LowActivedown
2026-09-0129LowActivedown
2026-08-3153MediumActiveup
2026-08-3053MediumActiveup
2026-08-2953MediumActiveup
2026-08-2853MediumActiveup
2026-08-2753MediumActiveup
2026-08-2653MediumActiveup
2026-08-2553MediumActiveup
2026-08-2453MediumActiveup
2026-08-2353MediumActiveup
2026-08-2253MediumActiveup
2026-08-2153MediumActiveup
2026-08-2053MediumActiveup
2026-08-1953MediumActiveup
2026-08-1853MediumActiveup
2026-08-1753MediumActiveup
2026-08-1653MediumActiveup
2026-08-1553MediumActiveup
2026-08-1453MediumActiveup
2026-08-1353MediumActiveup
2026-08-1253MediumActiveup
2026-08-1153MediumActiveup
2026-08-1053MediumActiveup
2026-08-0953MediumActiveup
2026-08-0853MediumActiveup
2026-08-0753MediumActiveup
2026-08-0653MediumActiveup
2026-08-0553MediumActiveup
2026-08-0453MediumActiveup
2026-08-0353MediumActiveup
2026-08-0253MediumActiveup
2026-08-0153MediumActiveup
2026-07-3153MediumActiveup
2026-07-3053MediumActiveup
2026-07-2953MediumActiveup
2026-07-2853MediumActiveup
2026-07-2753MediumActiveup
2026-07-2653MediumActiveup
2026-07-2553MediumActiveup
2026-07-2453MediumActiveup
2026-07-2353MediumActiveup
2026-07-2253MediumActiveup
2026-07-2153MediumActiveup
2026-07-2053MediumActiveup
2026-07-1937LowActiveup

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 1, 2026
    Sato Score tier: Medium → Low
    Score 53 → 29.
  2. Aug 1, 2026
    Sato Hub began tracking this listing
  3. Jul 20, 2026
    Edited: mcp endpoint url
  4. Jul 20, 2026
    Edited: deploy spec
  5. Jul 19, 2026
    Listed on Sato Hub

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.