Sato Hub
← SOLx402 MCP Server verification record

Score history

SOLx402 MCP Server

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 57d

-14

Days measured

57

Days missed

0

Sato Score, daily

2026-07-19 → 2026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (41 → 29). Not a change by the project.2026-07-19: 41 (Medium)2026-07-20: 29 (Low)2026-07-21: 35 (Low)2026-07-22: 35 (Low)2026-07-23: 35 (Low)2026-07-24: 35 (Low)2026-07-25: 35 (Low)2026-07-26: 35 (Low)2026-07-27: 35 (Low)2026-07-28: 35 (Low)2026-07-29: 35 (Low)2026-07-30: 35 (Low)2026-07-31: 35 (Low)2026-08-01: 35 (Low)2026-08-02: 35 (Low)2026-08-03: 35 (Low)2026-08-04: 35 (Low)2026-08-05: 35 (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)41272026-07-192026-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, 1 caused by a revision of the scoring method.

DateFromToChangeCause
2026-08-063527-8the project
2026-07-212935+6the project
2026-07-204129-12Sato 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 & liveness5/35
35
Code transparency17/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance5/15
15
Independent verification0/10
10

The observed record

1.8% of Sato Hub's own daily checks succeeded over 57 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-19: answered our check2026-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-1327LowEarlydown
2026-09-1227LowEarlydown
2026-09-1127LowEarlydown
2026-09-1027LowEarlydown
2026-09-0927LowEarlydown
2026-09-0827LowEarlydown
2026-09-0727LowEarlydown
2026-09-0627LowEarlydown
2026-09-0527LowEarlydown
2026-09-0427LowEarlydown
2026-09-0327LowEarlydown
2026-09-0227LowEarlydown
2026-09-0127LowEarlydown
2026-08-3127LowEarlyunknown
2026-08-3027LowEarlyunknown
2026-08-2927LowEarlyunknown
2026-08-2827LowEarlyunknown
2026-08-2727LowEarlyunknown
2026-08-2627LowEarlyunknown
2026-08-2527LowEarlyunknown
2026-08-2427LowEarlyunknown
2026-08-2327LowEarlyunknown
2026-08-2227LowEarlyunknown
2026-08-2127LowEarlyunknown
2026-08-2027LowEarlyunknown
2026-08-1927LowEarlyunknown
2026-08-1827LowEarlyunknown
2026-08-1727LowEarlyunknown
2026-08-1627LowEarlyunknown
2026-08-1527LowEarlyunknown
2026-08-1427LowEarlyunknown
2026-08-1327LowEarlyunknown
2026-08-1227LowEarlyunknown
2026-08-1127LowEarlyunknown
2026-08-1027LowEarlyunknown
2026-08-0927LowEarlyunknown
2026-08-0827LowEarlyunknown
2026-08-0727LowEarlyunknown
2026-08-0627LowEarlyunknown
2026-08-0535LowEarlyunknown
2026-08-0435LowEarlyunknown
2026-08-0335LowEarlyunknown
2026-08-0235LowEarlyunknown
2026-08-0135LowEarlyunknown
2026-07-3135LowEarlyunknown
2026-07-3035LowEarlyunknown
2026-07-2935LowEarlyunknown
2026-07-2835LowEarlyunknown
2026-07-2735LowEarlyunknown
2026-07-2635LowEarlyunknown
2026-07-2535LowEarlyunknown
2026-07-2435LowEarlyunknown
2026-07-2335LowEarlyunknown
2026-07-2235LowEarlyunknown
2026-07-2135LowEarlyunknown
2026-07-2029LowEarlyunknown
2026-07-1941MediumEarlyup

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 20, 2026
    Sato Score tier: Medium → Low
    Score 41 → 29.
  3. Jul 19, 2026
    Listed on Sato Hub
  4. Jul 19, 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