Sato Hub
Hedera MCP verification record

Score history

Hedera 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

78

Change over 62d

+22

Days measured

62

Days missed

0

Sato Score, daily

2026-07-142026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (56 → 65). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (60 → 63). Not a change by the project.2026-07-14: 56 (Medium)2026-07-15: 56 (Medium)2026-07-16: 56 (Medium)2026-07-17: 56 (Medium)2026-07-18: 56 (Medium)2026-07-19: 56 (Medium)2026-07-20: 65 (Medium)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: 65 (Medium)2026-08-05: 65 (Medium)2026-08-06: 65 (Medium)2026-08-07: 65 (Medium)2026-08-08: 65 (Medium)2026-08-09: 65 (Medium)2026-08-10: 65 (Medium)2026-08-11: 65 (Medium)2026-08-12: 65 (Medium)2026-08-13: 65 (Medium)2026-08-14: 65 (Medium)2026-08-15: 65 (Medium)2026-08-16: 65 (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: 60 (Medium)2026-08-29: 60 (Medium)2026-08-30: 60 (Medium)2026-08-31: 60 (Medium)2026-09-01: 63 (Medium)2026-09-02: 63 (Medium)2026-09-03: 63 (Medium)2026-09-04: 63 (Medium)2026-09-05: 63 (Medium)2026-09-06: 63 (Medium)2026-09-07: 63 (Medium)2026-09-08: 63 (Medium)2026-09-09: 63 (Medium)2026-09-10: 78 (High)2026-09-11: 78 (High)2026-09-12: 78 (High)2026-09-13: 78 (High)5678782026-07-142026-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

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

DateFromToChangeCause
2026-09-106378+15the project
2026-09-016063+3Sato Hub changed the scoring method
2026-08-286560-5the project
2026-07-205665+9Sato 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 & demo6/10
10
Listing transparency & provenance10/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-1378HighActiveup
2026-09-1278HighActiveup
2026-09-1178HighActiveup
2026-09-1078HighActiveup
2026-09-0963MediumActiveup
2026-09-0863MediumActiveup
2026-09-0763MediumActiveup
2026-09-0663MediumActiveup
2026-09-0563MediumActiveup
2026-09-0463MediumActiveup
2026-09-0363MediumActiveup
2026-09-0263MediumActiveup
2026-09-0163MediumActiveup
2026-08-3160MediumActiveup
2026-08-3060MediumActiveup
2026-08-2960MediumActiveup
2026-08-2860MediumActiveup
2026-08-2765MediumActiveup
2026-08-2665MediumActiveup
2026-08-2565MediumActiveup
2026-08-2465MediumActiveup
2026-08-2365MediumActiveup
2026-08-2265MediumActiveup
2026-08-2165MediumActiveup
2026-08-2065MediumActiveup
2026-08-1965MediumActiveup
2026-08-1865MediumActiveup
2026-08-1765MediumActiveup
2026-08-1665MediumActiveup
2026-08-1565MediumActiveup
2026-08-1465MediumActiveup
2026-08-1365MediumActiveup
2026-08-1265MediumActiveup
2026-08-1165MediumActiveup
2026-08-1065MediumActiveup
2026-08-0965MediumActiveup
2026-08-0865MediumActiveup
2026-08-0765MediumActiveup
2026-08-0665MediumActiveup
2026-08-0565MediumActiveup
2026-08-0465MediumActiveup
2026-08-0365MediumActiveup
2026-08-0265MediumActiveup
2026-08-0165MediumActiveup
2026-07-3165MediumActiveup
2026-07-3065MediumActiveup
2026-07-2965MediumActiveup
2026-07-2865MediumActiveup
2026-07-2765MediumActiveup
2026-07-2665MediumActiveup
2026-07-2565MediumActiveup
2026-07-2465MediumActiveup
2026-07-2365MediumActiveup
2026-07-2265MediumActiveup
2026-07-2165MediumActiveup
2026-07-2065MediumActiveup
2026-07-1956MediumActiveup
2026-07-1856MediumActiveup
2026-07-1756MediumActiveup
2026-07-1656MediumActiveup
2026-07-1556MediumActiveup
2026-07-1456MediumActiveup

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 10, 2026
    Sato Score tier: Medium → High
    Score 63 → 78.
  2. Sep 10, 2026
    Active again — shipped after a quiet spell
  3. Jul 21, 2026
    Verified: deploy spec
  4. Jul 14, 2026
    Enriched: deployment options
  5. Jul 14, 2026
    Auto-enriched: creator profile url
  6. Jul 14, 2026
    Listed on Sato Hub
  7. Jul 14, 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.