Sato Hub
CoinStats MCP verification record

Score history

CoinStats 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

65

Change over 63d

-8

Days measured

63

Days missed

0

Sato Score, daily

2026-07-132026-09-13
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-07-20: Sato Hub changed the scoring method (71 → 75). 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: 71 (High)2026-07-20: 75 (High)2026-07-21: 75 (High)2026-07-22: 75 (High)2026-07-23: 75 (High)2026-07-24: 75 (High)2026-07-25: 75 (High)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: 75 (High)2026-08-28: 75 (High)2026-08-29: 75 (High)2026-08-30: 75 (High)2026-08-31: 75 (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: 65 (Medium)7375652026-07-132026-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

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

DateFromToChangeCause
2026-09-137565-10the project
2026-08-276575+10the project
2026-07-267565-10the project
2026-07-207175+4Sato Hub changed the scoring method
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 verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification4/10
10

The observed record

8.1% 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: failed, unattributable2026-07-20: failed, unattributable2026-07-21: failed, unattributable2026-07-22: failed, unattributable2026-07-23: failed, unattributable2026-07-24: failed, unattributable2026-07-25: failed, unattributable2026-07-26: failed, unattributable2026-07-27: failed, unattributable2026-07-28: failed, unattributable2026-07-29: failed, unattributable2026-07-30: failed, unattributable2026-07-31: failed, unattributable2026-08-01: failed, unattributable2026-08-02: failed, unattributable2026-08-03: failed, unattributable2026-08-04: failed, unattributable2026-08-05: failed, unattributable2026-08-06: failed, unattributable2026-08-07: failed, unattributable2026-08-08: failed, unattributable2026-08-09: failed, unattributable2026-08-10: failed, unattributable2026-08-11: failed, unattributable2026-08-12: failed, unattributable2026-08-13: failed, unattributable2026-08-14: failed, unattributable2026-08-15: failed, unattributable2026-08-16: failed, unattributable2026-08-17: failed, unattributable2026-08-18: failed, unattributable2026-08-19: failed, unattributable2026-08-20: failed, unattributable2026-08-21: failed, unattributable2026-08-22: failed, unattributable2026-08-23: failed, unattributable2026-08-24: failed, unattributable2026-08-25: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-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: the host answered with an error2026-09-12: the host answered with an error2026-09-13: the host answered with an error
  • 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-1365MediumActivedown
2026-09-1275HighActivedown
2026-09-1175HighActivedown
2026-09-1075HighActivedown
2026-09-0975HighActivedown
2026-09-0875HighActivedown
2026-09-0775HighActivedown
2026-09-0675HighActivedown
2026-09-0575HighActivedown
2026-09-0475HighActivedown
2026-09-0375HighActivedown
2026-09-0275HighActivedown
2026-09-0175HighActivedown
2026-08-3175HighActiveunknown
2026-08-3075HighActiveunknown
2026-08-2975HighActiveunknown
2026-08-2875HighActiveunknown
2026-08-2775HighActiveunknown
2026-08-2665MediumActiveunknown
2026-08-2565MediumActiveunknown
2026-08-2465MediumActiveunknown
2026-08-2365MediumActiveunknown
2026-08-2265MediumActiveunknown
2026-08-2165MediumActiveunknown
2026-08-2065MediumActiveunknown
2026-08-1965MediumActiveunknown
2026-08-1865MediumActiveunknown
2026-08-1765MediumActiveunknown
2026-08-1665MediumActiveunknown
2026-08-1565MediumActiveunknown
2026-08-1465MediumActiveunknown
2026-08-1365MediumActiveunknown
2026-08-1265MediumActiveunknown
2026-08-1165MediumActiveunknown
2026-08-1065MediumActiveunknown
2026-08-0965MediumActiveunknown
2026-08-0865MediumActiveunknown
2026-08-0765MediumActiveunknown
2026-08-0665MediumActiveunknown
2026-08-0565MediumActiveunknown
2026-08-0465MediumActiveunknown
2026-08-0365MediumActiveunknown
2026-08-0265MediumActiveunknown
2026-08-0165MediumActiveunknown
2026-07-3165MediumActiveunknown
2026-07-3065MediumActiveunknown
2026-07-2965MediumActiveunknown
2026-07-2865MediumActiveunknown
2026-07-2765MediumActiveunknown
2026-07-2665MediumActiveunknown
2026-07-2575HighActiveunknown
2026-07-2475HighActiveunknown
2026-07-2375HighActiveunknown
2026-07-2275HighActiveunknown
2026-07-2175HighActiveunknown
2026-07-2075HighActiveunknown
2026-07-1971HighActiveunknown
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. Sep 13, 2026
    Sato Score tier: High → Medium
    Score 75 → 65.
  2. Aug 27, 2026
    Sato Score tier: Medium → High
    Score 65 → 75.
  3. Jul 26, 2026
    Sato Score tier: High → Medium
    Score 75 → 65.
  4. Jul 20, 2026
    Edited: mcp endpoint url
  5. Jul 19, 2026
    Edited: mcp endpoint url
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 13, 2026
    Listed on Sato Hub
  8. Jul 13, 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.