Sato Hub
Score history

Algorand MCP

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

Score today

72

Change over 109d

-1

Days measured

109

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-10-206472+8the project
2026-09-077464-10the project
2026-09-017174+3Sato Hub changed the scoring method
2026-08-276171+10the project
2026-07-197161-10the project
2026-07-157071+1Sato Hub changed the scoring method
2026-07-147370-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 & liveness25/35
35
Code transparency18/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification3/10
10

The observed record

100% of 108 daily checks since 2026-07-14 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-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: 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 check2026-09-14: answered our check2026-09-15: answered our check2026-09-16: answered our check2026-09-17: answered our check2026-09-18: answered our check2026-09-19: answered our check2026-09-20: answered our check2026-09-21: answered our check2026-09-22: answered our check2026-09-23: answered our check2026-09-24: answered our check2026-09-25: answered our check2026-09-26: answered our check2026-09-27: answered our check2026-09-28: answered our check2026-09-29: answered our check2026-09-30: answered our check2026-10-01: answered our check2026-10-02: answered our check2026-10-03: answered our check2026-10-04: answered our check2026-10-05: answered our check2026-10-06: answered our check2026-10-07: answered our check2026-10-08: answered our check2026-10-09: answered our check2026-10-10: answered our check2026-10-11: answered our check2026-10-12: answered our check2026-10-13: answered our check2026-10-14: answered our check2026-10-15: answered our check2026-10-16: answered our check2026-10-17: answered our check2026-10-18: answered our check2026-10-19: answered our check2026-10-20: answered our check2026-10-21: answered our check2026-10-22: answered our check2026-10-23: answered our check2026-10-24: answered our check2026-10-25: answered our check2026-10-26: answered our check2026-10-27: answered our check2026-10-28: answered our check2026-10-29: 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-10-2972HighActiveup
2026-10-2872HighActiveup
2026-10-2772HighActiveup
2026-10-2672HighActiveup
2026-10-2572HighActiveup
2026-10-2472HighActiveup
2026-10-2372HighActiveup
2026-10-2272HighActiveup
2026-10-2172HighActiveup
2026-10-2072HighActiveup
2026-10-1964MediumActiveup
2026-10-1864MediumActiveup
2026-10-1764MediumActiveup
2026-10-1664MediumActiveup
2026-10-1564MediumActiveup
2026-10-1464MediumActiveup
2026-10-1364MediumActiveup
2026-10-1264MediumActiveup
2026-10-1164MediumActiveup
2026-10-1064MediumActiveup
2026-10-0964MediumActiveup
2026-10-0864MediumActiveup
2026-10-0764MediumActiveup
2026-10-0664MediumActiveup
2026-10-0564MediumActiveup
2026-10-0464MediumActiveup
2026-10-0364MediumActiveup
2026-10-0264MediumActiveup
2026-10-0164MediumActiveup
2026-09-3064MediumActiveup
2026-09-2964MediumActiveup
2026-09-2864MediumActiveup
2026-09-2764MediumActiveup
2026-09-2664MediumActiveup
2026-09-2564MediumActiveup
2026-09-2464MediumActiveup
2026-09-2364MediumActiveup
2026-09-2264MediumActiveup
2026-09-2164MediumActiveup
2026-09-2064MediumActiveup
2026-09-1964MediumActiveup
2026-09-1864MediumActiveup
2026-09-1764MediumActiveup
2026-09-1664MediumActiveup
2026-09-1564MediumActiveup
2026-09-1464MediumActiveup
2026-09-1364MediumActiveup
2026-09-1264MediumActiveup
2026-09-1164MediumActiveup
2026-09-1064MediumActiveup
2026-09-0964MediumActiveup
2026-09-0864MediumActiveup
2026-09-0764MediumActiveup
2026-09-0674HighActiveup
2026-09-0574HighActiveup
2026-09-0474HighActiveup
2026-09-0374HighActiveup
2026-09-0274HighActiveup
2026-09-0174HighActiveup
2026-08-3171HighActiveup
2026-08-3071HighActiveup
2026-08-2971HighActiveup
2026-08-2871HighActiveup
2026-08-2771HighActiveup
2026-08-2661MediumActiveup
2026-08-2561MediumActiveup
2026-08-2461MediumActiveup
2026-08-2361MediumActiveup
2026-08-2261MediumActiveup
2026-08-2161MediumActiveup
2026-08-2061MediumActiveup
2026-08-1961MediumActiveup
2026-08-1861MediumActiveup
2026-08-1761MediumActiveup
2026-08-1661MediumActiveup
2026-08-1561MediumActiveup
2026-08-1461MediumActiveup
2026-08-1361MediumActiveup
2026-08-1261MediumActiveup
2026-08-1161MediumActiveup
2026-08-1061MediumActiveup
2026-08-0961MediumActiveup
2026-08-0861MediumActiveup
2026-08-0761MediumActiveup
2026-08-0661MediumActiveup
2026-08-0561MediumActiveup
2026-08-0461MediumActiveup
2026-08-0361MediumActiveup
2026-08-0261MediumActiveup
2026-08-0161MediumActiveup
2026-07-3161MediumActiveup
2026-07-3061MediumActiveup
2026-07-2961MediumActiveup
2026-07-2861MediumActiveup
2026-07-2761MediumActiveup
2026-07-2661MediumActiveup
2026-07-2561MediumActiveup
2026-07-2461MediumActiveup
2026-07-2361MediumActiveup
2026-07-2261MediumActiveup
2026-07-2161MediumActiveup
2026-07-2061MediumActiveup
2026-07-1961MediumActiveup
2026-07-1871HighActiveup
2026-07-1771HighActiveup
2026-07-1671HighActiveup
2026-07-1571HighActiveup
2026-07-1470HighActiveup
2026-07-1373HighActivenot checked

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. Oct 20, 2026
    Sato Score tier: Medium → High
    Score 64 → 72.
  2. Oct 19, 2026
    Verified: deploy spec
  3. Sep 7, 2026
    Sato Score tier: High → Medium
    Score 74 → 64.
  4. Aug 27, 2026
    Sato Score tier: Medium → High
    Score 61 → 71.
  5. Aug 1, 2026
    Sato Hub began tracking this listing
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 13, 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.