Sato Hub
← CoinMarketCap MCP verification record

Score history

CoinMarketCap 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

27

Change over 63d

+5

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-07-202327+4Sato Hub changed the scoring method
2026-07-193523-12the project
2026-07-142235+13Sato 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 & liveness8/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance9/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-1327LowUnknowndown
2026-09-1227LowUnknowndown
2026-09-1127LowUnknowndown
2026-09-1027LowUnknowndown
2026-09-0927LowUnknowndown
2026-09-0827LowUnknowndown
2026-09-0727LowUnknowndown
2026-09-0627LowUnknowndown
2026-09-0527LowUnknowndown
2026-09-0427LowUnknowndown
2026-09-0327LowUnknowndown
2026-09-0227LowUnknowndown
2026-09-0127LowUnknowndown
2026-08-3127LowUnknownunknown
2026-08-3027LowUnknownunknown
2026-08-2927LowUnknownunknown
2026-08-2827LowUnknownunknown
2026-08-2727LowUnknownunknown
2026-08-2627LowUnknownunknown
2026-08-2527LowUnknownunknown
2026-08-2427LowUnknownunknown
2026-08-2327LowUnknownunknown
2026-08-2227LowUnknownunknown
2026-08-2127LowUnknownunknown
2026-08-2027LowUnknownunknown
2026-08-1927LowUnknownunknown
2026-08-1827LowUnknownunknown
2026-08-1727LowUnknownunknown
2026-08-1627LowUnknownunknown
2026-08-1527LowUnknownunknown
2026-08-1427LowUnknownunknown
2026-08-1327LowUnknownunknown
2026-08-1227LowUnknownunknown
2026-08-1127LowUnknownunknown
2026-08-1027LowUnknownunknown
2026-08-0927LowUnknownunknown
2026-08-0827LowUnknownunknown
2026-08-0727LowUnknownunknown
2026-08-0627LowUnknownunknown
2026-08-0527LowUnknownunknown
2026-08-0427LowUnknownunknown
2026-08-0327LowUnknownunknown
2026-08-0227LowUnknownunknown
2026-08-0127LowUnknownunknown
2026-07-3127LowUnknownunknown
2026-07-3027LowUnknownunknown
2026-07-2927LowUnknownunknown
2026-07-2827LowUnknownunknown
2026-07-2727LowUnknownunknown
2026-07-2627LowUnknownunknown
2026-07-2527LowUnknownunknown
2026-07-2427LowUnknownunknown
2026-07-2327LowUnknownunknown
2026-07-2227LowUnknownunknown
2026-07-2127LowUnknownunknown
2026-07-2027LowUnknownunknown
2026-07-1923LowUnknownunknown
2026-07-1835LowUnknownup
2026-07-1735LowUnknownup
2026-07-1635LowUnknownup
2026-07-1535LowUnknownup
2026-07-1435LowUnknownup
2026-07-1322LowUnknownnot 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. Jul 20, 2026
    Edited: mcp endpoint url
  2. Jul 19, 2026
    Edited: mcp endpoint url
  3. Jul 14, 2026
    Enriched: deployment options
  4. Jul 14, 2026
    Auto-enriched: has pricing
  5. Jul 13, 2026
    Listed on Sato Hub
  6. 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.
← Verification recordThis week’s moversDispute this score