Sato Hub
Bankless Onchain MCP verification record

Score history

Bankless Onchain 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

70

Change over 90d

+36

Days measured

90

Days missed

4

Sato Score, daily

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

4 days in this span have no reading; the line breaks there rather than joining across them. 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

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

DateFromToChangeCause
2026-09-016770+3Sato Hub changed the scoring method
2026-07-145167+16Sato Hub changed the scoring method
2026-06-253551+16Sato Hub changed the scoring method
2026-06-173435+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 & liveness20/35
35
Code transparency18/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance15/15
15
Independent verification3/10
10

The observed record

100% of Sato Hub's own daily checks succeeded over 62 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-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 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-1370HighUnknownup
2026-09-1270HighUnknownup
2026-09-1170HighUnknownup
2026-09-1070HighUnknownup
2026-09-0970HighUnknownup
2026-09-0870HighUnknownup
2026-09-0770HighUnknownup
2026-09-0670HighUnknownup
2026-09-0570HighUnknownup
2026-09-0470HighUnknownup
2026-09-0370HighUnknownup
2026-09-0270HighUnknownup
2026-09-0170HighUnknownup
2026-08-3167MediumUnknownup
2026-08-3067MediumUnknownup
2026-08-2967MediumUnknownup
2026-08-2867MediumUnknownup
2026-08-2767MediumUnknownup
2026-08-2667MediumUnknownup
2026-08-2567MediumUnknownup
2026-08-2467MediumUnknownup
2026-08-2367MediumUnknownup
2026-08-2267MediumUnknownup
2026-08-2167MediumUnknownup
2026-08-2067MediumUnknownup
2026-08-1967MediumUnknownup
2026-08-1867MediumUnknownup
2026-08-1767MediumUnknownup
2026-08-1667MediumUnknownup
2026-08-1567MediumUnknownup
2026-08-1467MediumUnknownup
2026-08-1367MediumUnknownup
2026-08-1267MediumUnknownup
2026-08-1167MediumUnknownup
2026-08-1067MediumUnknownup
2026-08-0967MediumUnknownup
2026-08-0867MediumUnknownup
2026-08-0767MediumUnknownup
2026-08-0667MediumUnknownup
2026-08-0567MediumUnknownup
2026-08-0467MediumUnknownup
2026-08-0367MediumUnknownup
2026-08-0267MediumUnknownup
2026-08-0167MediumUnknownup
2026-07-3167MediumUnknownup
2026-07-3067MediumUnknownup
2026-07-2967MediumUnknownup
2026-07-2867MediumUnknownup
2026-07-2767MediumUnknownup
2026-07-2667MediumUnknownup
2026-07-2567MediumUnknownup
2026-07-2467MediumUnknownup
2026-07-2367MediumUnknownup
2026-07-2267MediumUnknownup
2026-07-2167MediumUnknownup
2026-07-2067MediumUnknownup
2026-07-1967MediumUnknownup
2026-07-1867MediumUnknownup
2026-07-1767MediumUnknownup
2026-07-1667MediumUnknownup
2026-07-1567MediumUnknownup
2026-07-1467MediumUnknownup
2026-07-1351MediumUnknownnot checked
2026-07-1251MediumUnknownnot checked
2026-07-1151MediumUnknownnot checked
2026-07-1051MediumUnknownnot checked
2026-07-0951MediumUnknownnot checked
2026-07-0851MediumUnknownnot checked
2026-07-0751MediumUnknownnot checked
2026-07-0651MediumUnknownnot checked
2026-07-0551MediumUnknownnot checked
2026-07-0451MediumUnknownnot checked
2026-07-0351MediumUnknownnot checked
2026-07-0251MediumUnknownnot checked
2026-07-0151MediumUnknownnot checked
2026-06-3051MediumUnknownnot checked
2026-06-2751MediumUnknownnot checked
2026-06-2651MediumUnknownnot checked
2026-06-2551MediumUnknownnot checked
2026-06-2435LowUnknownnot checked
2026-06-2235LowUnknownnot checked
2026-06-2035LowUnknownnot checked
2026-06-1935LowUnknownnot checked
2026-06-1835LowUnknownnot checked
2026-06-1735LowUnknownnot checked
2026-06-1634LowUnknownnot checked
2026-06-1534LowUnknownnot checked
2026-06-1434LowUnknownnot checked
2026-06-1334LowUnknownnot checked
2026-06-1234LowUnknownnot checked
2026-06-11unknownUnknownnot 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. Sep 7, 2026
    Verified: deploy spec
  2. Sep 1, 2026
    Sato Score tier: Medium → High
    Score 67 → 70.
  3. Jun 25, 2026
    Enriched: marketplace notes
  4. Jun 25, 2026
    Auto-enriched: creator name, creator profile url, deployment options, supported integrations +2 more
  5. Jun 25, 2026
    Sato Score tier: Low → Medium
    Score 35 → 51.
  6. Jun 12, 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.