Sato Hub
← Across MCP verification record

Score history

Across 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

83

Change over 63d

+40

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-018083+3Sato Hub changed the scoring method
2026-07-157980+1Sato Hub changed the scoring method
2026-07-144379+36Sato 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 transparency17/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance12/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-1383HighActiveup
2026-09-1283HighActiveup
2026-09-1183HighActiveup
2026-09-1083HighActiveup
2026-09-0983HighActiveup
2026-09-0883HighActiveup
2026-09-0783HighActiveup
2026-09-0683HighActiveup
2026-09-0583HighActiveup
2026-09-0483HighActiveup
2026-09-0383HighActiveup
2026-09-0283HighActiveup
2026-09-0183HighActiveup
2026-08-3180HighActiveup
2026-08-3080HighActiveup
2026-08-2980HighActiveup
2026-08-2880HighActiveup
2026-08-2780HighActiveup
2026-08-2680HighActiveup
2026-08-2580HighActiveup
2026-08-2480HighActiveup
2026-08-2380HighActiveup
2026-08-2280HighActiveup
2026-08-2180HighActiveup
2026-08-2080HighActiveup
2026-08-1980HighActiveup
2026-08-1880HighActiveup
2026-08-1780HighActiveup
2026-08-1680HighActiveup
2026-08-1580HighActiveup
2026-08-1480HighActiveup
2026-08-1380HighActiveup
2026-08-1280HighActiveup
2026-08-1180HighActiveup
2026-08-1080HighActiveup
2026-08-0980HighActiveup
2026-08-0880HighActiveup
2026-08-0780HighActiveup
2026-08-0680HighActiveup
2026-08-0580HighActiveup
2026-08-0480HighActiveup
2026-08-0380HighActiveup
2026-08-0280HighActiveup
2026-08-0180HighActiveup
2026-07-3180HighActiveup
2026-07-3080HighActiveup
2026-07-2980HighActiveup
2026-07-2880HighActiveup
2026-07-2780HighActiveup
2026-07-2680HighActiveup
2026-07-2580HighActiveup
2026-07-2480HighActiveup
2026-07-2380HighActiveup
2026-07-2280HighActiveup
2026-07-2180HighActiveup
2026-07-2080HighActiveup
2026-07-1980HighActiveup
2026-07-1880HighActiveup
2026-07-1780HighActiveup
2026-07-1680HighActiveup
2026-07-1580HighActiveup
2026-07-1479HighActiveup
2026-07-1343MediumActivenot 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 14, 2026
    Edited: mcp endpoint url
  2. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  3. Jul 14, 2026
    Sato Score tier: Medium → High
    Score 43 → 79.
  4. Jul 13, 2026
    Listed on Sato Hub
  5. 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