Sato Hub
Score history

Starknet MCP

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

Score today

65

Change over 109d

-5

Days measured

109

Days missed

0

Sato Score, daily

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

1 change attributable to the project, 4 caused by a revision of the scoring method.

DateFromToChangeCause
2026-10-257565-10the project
2026-09-017275+3Sato Hub changed the scoring method
2026-07-207172+1Sato Hub changed the scoring method
2026-07-156871+3Sato Hub changed the scoring method
2026-07-147068-2Sato 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 transparency19/20
20
Interface verifiability0/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-2965MediumActiveup
2026-10-2865MediumActiveup
2026-10-2765MediumActiveup
2026-10-2665MediumActiveup
2026-10-2565MediumActiveup
2026-10-2475HighActiveup
2026-10-2375HighActiveup
2026-10-2275HighActiveup
2026-10-2175HighActiveup
2026-10-2075HighActiveup
2026-10-1975HighActiveup
2026-10-1875HighActiveup
2026-10-1775HighActiveup
2026-10-1675HighActiveup
2026-10-1575HighActiveup
2026-10-1475HighActiveup
2026-10-1375HighActiveup
2026-10-1275HighActiveup
2026-10-1175HighActiveup
2026-10-1075HighActiveup
2026-10-0975HighActiveup
2026-10-0875HighActiveup
2026-10-0775HighActiveup
2026-10-0675HighActiveup
2026-10-0575HighActiveup
2026-10-0475HighActiveup
2026-10-0375HighActiveup
2026-10-0275HighActiveup
2026-10-0175HighActiveup
2026-09-3075HighActiveup
2026-09-2975HighActiveup
2026-09-2875HighActiveup
2026-09-2775HighActiveup
2026-09-2675HighActiveup
2026-09-2575HighActiveup
2026-09-2475HighActiveup
2026-09-2375HighActiveup
2026-09-2275HighActiveup
2026-09-2175HighActiveup
2026-09-2075HighActiveup
2026-09-1975HighActiveup
2026-09-1875HighActiveup
2026-09-1775HighActiveup
2026-09-1675HighActiveup
2026-09-1575HighActiveup
2026-09-1475HighActiveup
2026-09-1375HighActiveup
2026-09-1275HighActiveup
2026-09-1175HighActiveup
2026-09-1075HighActiveup
2026-09-0975HighActiveup
2026-09-0875HighActiveup
2026-09-0775HighActiveup
2026-09-0675HighActiveup
2026-09-0575HighActiveup
2026-09-0475HighActiveup
2026-09-0375HighActiveup
2026-09-0275HighActiveup
2026-09-0175HighActiveup
2026-08-3172HighActiveup
2026-08-3072HighActiveup
2026-08-2972HighActiveup
2026-08-2872HighActiveup
2026-08-2772HighActiveup
2026-08-2672HighActiveup
2026-08-2572HighActiveup
2026-08-2472HighActiveup
2026-08-2372HighActiveup
2026-08-2272HighActiveup
2026-08-2172HighActiveup
2026-08-2072HighActiveup
2026-08-1972HighActiveup
2026-08-1872HighActiveup
2026-08-1772HighActiveup
2026-08-1672HighActiveup
2026-08-1572HighActiveup
2026-08-1472HighActiveup
2026-08-1372HighActiveup
2026-08-1272HighActiveup
2026-08-1172HighActiveup
2026-08-1072HighActiveup
2026-08-0972HighActiveup
2026-08-0872HighActiveup
2026-08-0772HighActiveup
2026-08-0672HighActiveup
2026-08-0572HighActiveup
2026-08-0472HighActiveup
2026-08-0372HighActiveup
2026-08-0272HighActiveup
2026-08-0172HighActiveup
2026-07-3172HighActiveup
2026-07-3072HighActiveup
2026-07-2972HighActiveup
2026-07-2872HighActiveup
2026-07-2772HighActiveup
2026-07-2672HighActiveup
2026-07-2572HighActiveup
2026-07-2472HighActiveup
2026-07-2372HighActiveup
2026-07-2272HighActiveup
2026-07-2172HighActiveup
2026-07-2072HighActiveup
2026-07-1971HighActiveup
2026-07-1871HighActiveup
2026-07-1771HighActiveup
2026-07-1671HighActiveup
2026-07-1571HighActiveup
2026-07-1468MediumActiveup
2026-07-1370HighActivenot 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 25, 2026
    Sato Score tier: High → Medium
    Score 75 → 65.
  2. Sep 10, 2026
    New release published
  3. Aug 13, 2026
    New release published
  4. Aug 1, 2026
    Sato Hub began tracking this listing
  5. Jul 20, 2026
    Edited: deploy spec
  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.