Sato Hub
← Arcadia MCP verification record

Score history

Arcadia 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

76

Change over 63d

+23

Days measured

63

Days missed

0

Sato Score, daily

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

DateFromToChangeCause
2026-09-017376+3Sato Hub changed the scoring method
2026-07-207173+2Sato Hub changed the scoring method
2026-07-196171+10the project
2026-07-156061+1Sato Hub changed the scoring method
2026-07-145360+7Sato 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 verifiability8/10
10
Docs & demo0/10
10
Listing transparency & provenance11/15
15
Independent verification5/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-1376HighUnknownup
2026-09-1276HighUnknownup
2026-09-1176HighUnknownup
2026-09-1076HighUnknownup
2026-09-0976HighUnknownup
2026-09-0876HighUnknownup
2026-09-0776HighUnknownup
2026-09-0676HighUnknownup
2026-09-0576HighUnknownup
2026-09-0476HighUnknownup
2026-09-0376HighUnknownup
2026-09-0276HighUnknownup
2026-09-0176HighUnknownup
2026-08-3173HighUnknownup
2026-08-3073HighUnknownup
2026-08-2973HighUnknownup
2026-08-2873HighUnknownup
2026-08-2773HighUnknownup
2026-08-2673HighUnknownup
2026-08-2573HighUnknownup
2026-08-2473HighUnknownup
2026-08-2373HighUnknownup
2026-08-2273HighUnknownup
2026-08-2173HighUnknownup
2026-08-2073HighUnknownup
2026-08-1973HighUnknownup
2026-08-1873HighUnknownup
2026-08-1773HighUnknownup
2026-08-1673HighUnknownup
2026-08-1573HighUnknownup
2026-08-1473HighUnknownup
2026-08-1373HighUnknownup
2026-08-1273HighUnknownup
2026-08-1173HighUnknownup
2026-08-1073HighUnknownup
2026-08-0973HighUnknownup
2026-08-0873HighUnknownup
2026-08-0773HighUnknownup
2026-08-0673HighUnknownup
2026-08-0573HighUnknownup
2026-08-0473HighUnknownup
2026-08-0373HighUnknownup
2026-08-0273HighUnknownup
2026-08-0173HighUnknownup
2026-07-3173HighUnknownup
2026-07-3073HighUnknownup
2026-07-2973HighUnknownup
2026-07-2873HighUnknownup
2026-07-2773HighUnknownup
2026-07-2673HighUnknownup
2026-07-2573HighUnknownup
2026-07-2473HighUnknownup
2026-07-2373HighUnknownup
2026-07-2273HighUnknownup
2026-07-2173HighUnknownup
2026-07-2073HighUnknownup
2026-07-1971HighUnknownup
2026-07-1861MediumUnknownup
2026-07-1761MediumUnknownup
2026-07-1661MediumUnknownup
2026-07-1561MediumUnknownup
2026-07-1460MediumUnknownup
2026-07-1353MediumUnknownnot 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. Aug 11, 2026
    Active again — shipped after a quiet spell
  2. Aug 10, 2026
    New release published
  3. Jul 21, 2026
    Verified: deploy spec
  4. Jul 20, 2026
    Edited: mcp endpoint url
  5. Jul 19, 2026
    Edited: mcp endpoint url
  6. Jul 19, 2026
    Sato Score tier: Medium → High
    Score 61 → 71.
  7. Jul 14, 2026
    Enriched: deployment options, supported integrations
  8. Jul 13, 2026
    Edited: website url
  9. Jul 13, 2026
    Listed on Sato Hub
  10. 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