Sato Hub
← Rootstock MCP Server verification record

Score history

Rootstock 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

64

Change over 62d

+17

Days measured

62

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-016164+3Sato Hub changed the scoring method
2026-08-157161-10the project
2026-07-206371+8Sato Hub changed the scoring method
2026-07-154763+16Sato 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 transparency17/20
20
Interface verifiability8/10
10
Docs & demo0/10
10
Listing transparency & provenance11/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-1364MediumUnknownup
2026-09-1264MediumUnknownup
2026-09-1164MediumUnknownup
2026-09-1064MediumUnknownup
2026-09-0964MediumUnknownup
2026-09-0864MediumUnknownup
2026-09-0764MediumUnknownup
2026-09-0664MediumUnknownup
2026-09-0564MediumUnknownup
2026-09-0464MediumUnknownup
2026-09-0364MediumUnknownup
2026-09-0264MediumUnknownup
2026-09-0164MediumUnknownup
2026-08-3161MediumUnknownup
2026-08-3061MediumUnknownup
2026-08-2961MediumUnknownup
2026-08-2861MediumUnknownup
2026-08-2761MediumUnknownup
2026-08-2661MediumUnknownup
2026-08-2561MediumUnknownup
2026-08-2461MediumUnknownup
2026-08-2361MediumUnknownup
2026-08-2261MediumUnknownup
2026-08-2161MediumUnknownup
2026-08-2061MediumUnknownup
2026-08-1961MediumUnknownup
2026-08-1861MediumUnknownup
2026-08-1761MediumUnknownup
2026-08-1661MediumUnknownup
2026-08-1561MediumUnknownup
2026-08-1471HighUnknownup
2026-08-1371HighUnknownup
2026-08-1271HighUnknownup
2026-08-1171HighUnknownup
2026-08-1071HighUnknownup
2026-08-0971HighUnknownup
2026-08-0871HighUnknownup
2026-08-0771HighUnknownup
2026-08-0671HighUnknownup
2026-08-0571HighUnknownup
2026-08-0471HighUnknownup
2026-08-0371HighUnknownup
2026-08-0271HighUnknownup
2026-08-0171HighUnknownup
2026-07-3171HighUnknownup
2026-07-3071HighUnknownup
2026-07-2971HighUnknownup
2026-07-2871HighUnknownup
2026-07-2771HighUnknownup
2026-07-2671HighUnknownup
2026-07-2571HighUnknownup
2026-07-2471HighUnknownup
2026-07-2371HighUnknownup
2026-07-2271HighUnknownup
2026-07-2171HighUnknownup
2026-07-2071HighUnknownup
2026-07-1963MediumUnknownup
2026-07-1863MediumUnknownup
2026-07-1763MediumUnknownup
2026-07-1663MediumUnknownup
2026-07-1563MediumUnknownup
2026-07-1447MediumUnknownup

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. Aug 15, 2026
    Sato Score tier: High → Medium
    Score 71 → 61.
  2. Jul 21, 2026
    Verified: deploy spec
  3. Jul 20, 2026
    Sato Score tier: Medium → High
    Score 63 → 71.
  4. Jul 15, 2026
    Active again — shipped after a quiet spell
  5. Jul 15, 2026
    New release published
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 14, 2026
    Listed on Sato Hub
  8. Jul 14, 2026
    New release published
  9. 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.
← Verification recordThis week’s moversDispute this score