Sato Hub
← Alby MCP verification record

Score history

Alby 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

54

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

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

DateFromToChangeCause
2026-08-136454-10the project
2026-08-084264+22the project
2026-07-194942-7the project
2026-07-154649+3Sato Hub changed the scoring method
2026-07-143146+15Sato 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 transparency18/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance11/15
15
Independent verification0/10
10

The observed record

8.1% 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: failed, unattributable2026-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-1354MediumActivedown
2026-09-1254MediumActivedown
2026-09-1154MediumActivedown
2026-09-1054MediumActivedown
2026-09-0954MediumActivedown
2026-09-0854MediumActivedown
2026-09-0754MediumActivedown
2026-09-0654MediumActivedown
2026-09-0554MediumActivedown
2026-09-0454MediumActivedown
2026-09-0354MediumActivedown
2026-09-0254MediumActivedown
2026-09-0154MediumActivedown
2026-08-3154MediumActiveunknown
2026-08-3054MediumActiveunknown
2026-08-2954MediumActiveunknown
2026-08-2854MediumActiveunknown
2026-08-2754MediumActiveunknown
2026-08-2654MediumActiveunknown
2026-08-2554MediumActiveunknown
2026-08-2454MediumActiveunknown
2026-08-2354MediumActiveunknown
2026-08-2254MediumActiveunknown
2026-08-2154MediumActiveunknown
2026-08-2054MediumActiveunknown
2026-08-1954MediumActiveunknown
2026-08-1854MediumActiveunknown
2026-08-1754MediumActiveunknown
2026-08-1654MediumActiveunknown
2026-08-1554MediumActiveunknown
2026-08-1454MediumActiveunknown
2026-08-1354MediumActiveunknown
2026-08-1264MediumActiveunknown
2026-08-1164MediumActiveunknown
2026-08-1064MediumActiveunknown
2026-08-0964MediumActiveunknown
2026-08-0864MediumActiveunknown
2026-08-0742MediumActiveunknown
2026-08-0642MediumActiveunknown
2026-08-0542MediumActiveunknown
2026-08-0442MediumActiveunknown
2026-08-0342MediumActiveunknown
2026-08-0242MediumActiveunknown
2026-08-0142MediumActiveunknown
2026-07-3142MediumActiveunknown
2026-07-3042MediumActiveunknown
2026-07-2942MediumActiveunknown
2026-07-2842MediumActiveunknown
2026-07-2742MediumActiveunknown
2026-07-2642MediumActiveunknown
2026-07-2542MediumActiveunknown
2026-07-2442MediumActiveunknown
2026-07-2342MediumActiveunknown
2026-07-2242MediumActiveunknown
2026-07-2142MediumActiveunknown
2026-07-2042MediumActiveunknown
2026-07-1942MediumActiveunknown
2026-07-1849MediumActiveup
2026-07-1749MediumActiveup
2026-07-1649MediumActiveup
2026-07-1549MediumActiveup
2026-07-1446MediumActiveup
2026-07-1331LowActivenot 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 8, 2026
    Active again — shipped after a quiet spell
  2. Jul 20, 2026
    Edited: mcp endpoint url
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  5. Jul 14, 2026
    Sato Score tier: Low → Medium
    Score 31 → 46.
  6. Jul 13, 2026
    Listed on Sato Hub
  7. 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