Sato Hub
Alpaca MCP Server verification record

Score history

Alpaca 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

69

Change over 63d

+36

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-016669+3Sato Hub changed the scoring method
2026-08-255666+10the project
2026-08-016656-10the project
2026-07-154766+19Sato Hub changed the scoring method
2026-07-143347+14Sato 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 transparency11/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance14/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-1369MediumActiveup
2026-09-1269MediumActiveup
2026-09-1169MediumActiveup
2026-09-1069MediumActiveup
2026-09-0969MediumActiveup
2026-09-0869MediumActiveup
2026-09-0769MediumActiveup
2026-09-0669MediumActiveup
2026-09-0569MediumActiveup
2026-09-0469MediumActiveup
2026-09-0369MediumActiveup
2026-09-0269MediumActiveup
2026-09-0169MediumActiveup
2026-08-3166MediumActiveup
2026-08-3066MediumActiveup
2026-08-2966MediumActiveup
2026-08-2866MediumActiveup
2026-08-2766MediumActiveup
2026-08-2666MediumActiveup
2026-08-2566MediumActiveup
2026-08-2456MediumActiveup
2026-08-2356MediumActiveup
2026-08-2256MediumActiveup
2026-08-2156MediumActiveup
2026-08-2056MediumActiveup
2026-08-1956MediumActiveup
2026-08-1856MediumActiveup
2026-08-1756MediumActiveup
2026-08-1656MediumActiveup
2026-08-1556MediumActiveup
2026-08-1456MediumActiveup
2026-08-1356MediumActiveup
2026-08-1256MediumActiveup
2026-08-1156MediumActiveup
2026-08-1056MediumActiveup
2026-08-0956MediumActiveup
2026-08-0856MediumActiveup
2026-08-0756MediumActiveup
2026-08-0656MediumActiveup
2026-08-0556MediumActiveup
2026-08-0456MediumActiveup
2026-08-0356MediumActiveup
2026-08-0256MediumActiveup
2026-08-0156MediumActiveup
2026-07-3166MediumActiveup
2026-07-3066MediumActiveup
2026-07-2966MediumActiveup
2026-07-2866MediumActiveup
2026-07-2766MediumActiveup
2026-07-2666MediumActiveup
2026-07-2566MediumActiveup
2026-07-2466MediumActiveup
2026-07-2366MediumActiveup
2026-07-2266MediumActiveup
2026-07-2166MediumActiveup
2026-07-2066MediumActiveup
2026-07-1966MediumActiveup
2026-07-1866MediumActiveup
2026-07-1766MediumActiveup
2026-07-1666MediumActiveup
2026-07-1566MediumActiveup
2026-07-1447MediumActiveup
2026-07-1333LowActivenot 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
    Auto-enriched: deployment options, supported integrations, x url
  2. Jul 14, 2026
    Sato Score tier: Low → Medium
    Score 33 → 47.
  3. Jul 13, 2026
    Listed on Sato Hub
  4. 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.