Sato Hub
Zerion MCP verification record

Score history

Zerion 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

67

Change over 63d

+45

Days measured

63

Days missed

0

Sato Score, daily

2026-07-132026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (22 → 40). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (57 → 60). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (64 → 67). Not a change by the project.2026-07-13: 22 (Low)2026-07-14: 40 (Medium)2026-07-15: 40 (Medium)2026-07-16: 40 (Medium)2026-07-17: 40 (Medium)2026-07-18: 40 (Medium)2026-07-19: 57 (Medium)2026-07-20: 60 (Medium)2026-07-21: 60 (Medium)2026-07-22: 60 (Medium)2026-07-23: 60 (Medium)2026-07-24: 60 (Medium)2026-07-25: 60 (Medium)2026-07-26: 60 (Medium)2026-07-27: 60 (Medium)2026-07-28: 60 (Medium)2026-07-29: 60 (Medium)2026-07-30: 60 (Medium)2026-07-31: 60 (Medium)2026-08-01: 60 (Medium)2026-08-02: 60 (Medium)2026-08-03: 60 (Medium)2026-08-04: 60 (Medium)2026-08-05: 60 (Medium)2026-08-06: 60 (Medium)2026-08-07: 60 (Medium)2026-08-08: 60 (Medium)2026-08-09: 60 (Medium)2026-08-10: 60 (Medium)2026-08-11: 64 (Medium)2026-08-12: 64 (Medium)2026-08-13: 64 (Medium)2026-08-14: 64 (Medium)2026-08-15: 64 (Medium)2026-08-16: 64 (Medium)2026-08-17: 64 (Medium)2026-08-18: 64 (Medium)2026-08-19: 64 (Medium)2026-08-20: 64 (Medium)2026-08-21: 64 (Medium)2026-08-22: 64 (Medium)2026-08-23: 64 (Medium)2026-08-24: 64 (Medium)2026-08-25: 64 (Medium)2026-08-26: 64 (Medium)2026-08-27: 64 (Medium)2026-08-28: 64 (Medium)2026-08-29: 64 (Medium)2026-08-30: 64 (Medium)2026-08-31: 64 (Medium)2026-09-01: 67 (Medium)2026-09-02: 67 (Medium)2026-09-03: 67 (Medium)2026-09-04: 67 (Medium)2026-09-05: 67 (Medium)2026-09-06: 67 (Medium)2026-09-07: 67 (Medium)2026-09-08: 67 (Medium)2026-09-09: 67 (Medium)2026-09-10: 67 (Medium)2026-09-11: 67 (Medium)2026-09-12: 67 (Medium)2026-09-13: 67 (Medium)2267672026-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-016467+3Sato Hub changed the scoring method
2026-08-116064+4the project
2026-07-205760+3Sato Hub changed the scoring method
2026-07-194057+17the project
2026-07-142240+18Sato 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 transparency0/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance7/15
15
Independent verification9/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-1367MediumActiveup
2026-09-1267MediumActiveup
2026-09-1167MediumActiveup
2026-09-1067MediumActiveup
2026-09-0967MediumActiveup
2026-09-0867MediumActiveup
2026-09-0767MediumActiveup
2026-09-0667MediumActiveup
2026-09-0567MediumActiveup
2026-09-0467MediumActiveup
2026-09-0367MediumActiveup
2026-09-0267MediumActiveup
2026-09-0167MediumActiveup
2026-08-3164MediumActiveup
2026-08-3064MediumActiveup
2026-08-2964MediumActiveup
2026-08-2864MediumActiveup
2026-08-2764MediumActiveup
2026-08-2664MediumActiveup
2026-08-2564MediumActiveup
2026-08-2464MediumActiveup
2026-08-2364MediumActiveup
2026-08-2264MediumActiveup
2026-08-2164MediumActiveup
2026-08-2064MediumActiveup
2026-08-1964MediumActiveup
2026-08-1864MediumActiveup
2026-08-1764MediumActiveup
2026-08-1664MediumActiveup
2026-08-1564MediumActiveup
2026-08-1464MediumActiveup
2026-08-1364MediumActiveup
2026-08-1264MediumActiveup
2026-08-1164MediumActiveup
2026-08-1060MediumActiveup
2026-08-0960MediumActiveup
2026-08-0860MediumActiveup
2026-08-0760MediumActiveup
2026-08-0660MediumActiveup
2026-08-0560MediumActiveup
2026-08-0460MediumActiveup
2026-08-0360MediumActiveup
2026-08-0260MediumActiveup
2026-08-0160MediumActiveup
2026-07-3160MediumActiveup
2026-07-3060MediumActiveup
2026-07-2960MediumActiveup
2026-07-2860MediumActiveup
2026-07-2760MediumActiveup
2026-07-2660MediumActiveup
2026-07-2560MediumActiveup
2026-07-2460MediumActiveup
2026-07-2360MediumActiveup
2026-07-2260MediumActiveup
2026-07-2160MediumActiveup
2026-07-2060MediumActiveup
2026-07-1957MediumActiveup
2026-07-1840MediumActiveup
2026-07-1740MediumActiveup
2026-07-1640MediumActiveup
2026-07-1540MediumActiveup
2026-07-1440MediumActiveup
2026-07-1322LowActivenot 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 20, 2026
    Edited: mcp endpoint url
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 14, 2026
    Sato Score tier: Low → Medium
    Score 22 → 40.
  5. Jul 13, 2026
    Listed on Sato Hub
  6. 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.