Sato Hub
← eth-mcp verification record

Score history

eth-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

46

Change over 57d

+5

Days measured

57

Days missed

0

Sato Score, daily

2026-07-19 → 2026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (41 → 42). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (44 → 47). Not a change by the project.2026-07-19: 41 (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: 44 (Medium)2026-08-08: 44 (Medium)2026-08-09: 44 (Medium)2026-08-10: 44 (Medium)2026-08-11: 44 (Medium)2026-08-12: 44 (Medium)2026-08-13: 44 (Medium)2026-08-14: 44 (Medium)2026-08-15: 44 (Medium)2026-08-16: 44 (Medium)2026-08-17: 44 (Medium)2026-08-18: 44 (Medium)2026-08-19: 44 (Medium)2026-08-20: 44 (Medium)2026-08-21: 44 (Medium)2026-08-22: 44 (Medium)2026-08-23: 44 (Medium)2026-08-24: 44 (Medium)2026-08-25: 44 (Medium)2026-08-26: 44 (Medium)2026-08-27: 44 (Medium)2026-08-28: 44 (Medium)2026-08-29: 44 (Medium)2026-08-30: 44 (Medium)2026-08-31: 44 (Medium)2026-09-01: 47 (Medium)2026-09-02: 47 (Medium)2026-09-03: 47 (Medium)2026-09-04: 47 (Medium)2026-09-05: 47 (Medium)2026-09-06: 47 (Medium)2026-09-07: 32 (Low)2026-09-08: 46 (Medium)2026-09-09: 46 (Medium)2026-09-10: 46 (Medium)2026-09-11: 46 (Medium)2026-09-12: 46 (Medium)2026-09-13: 46 (Medium)4147462026-07-192026-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-09-083246+14the project
2026-09-074732-15the project
2026-09-014447+3Sato Hub changed the scoring method
2026-08-074244+2the project
2026-07-204142+1Sato 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 & liveness20/35
35
Code transparency16/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance8/15
15
Independent verification2/10
10

The observed record

98.2% of Sato Hub's own daily checks succeeded over 57 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-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: failed on our side — not attributable to the project2026-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-1346MediumEarlyup
2026-09-1246MediumEarlyup
2026-09-1146MediumEarlyup
2026-09-1046MediumEarlyup
2026-09-0946MediumEarlyup
2026-09-0846MediumEarlyup
2026-09-0732LowEarlyinconclusive
2026-09-0647MediumEarlyup
2026-09-0547MediumEarlyup
2026-09-0447MediumEarlyup
2026-09-0347MediumEarlyup
2026-09-0247MediumEarlyup
2026-09-0147MediumEarlyup
2026-08-3144MediumEarlyup
2026-08-3044MediumEarlyup
2026-08-2944MediumEarlyup
2026-08-2844MediumEarlyup
2026-08-2744MediumEarlyup
2026-08-2644MediumEarlyup
2026-08-2544MediumEarlyup
2026-08-2444MediumEarlyup
2026-08-2344MediumEarlyup
2026-08-2244MediumEarlyup
2026-08-2144MediumEarlyup
2026-08-2044MediumEarlyup
2026-08-1944MediumEarlyup
2026-08-1844MediumEarlyup
2026-08-1744MediumEarlyup
2026-08-1644MediumEarlyup
2026-08-1544MediumEarlyup
2026-08-1444MediumEarlyup
2026-08-1344MediumEarlyup
2026-08-1244MediumEarlyup
2026-08-1144MediumEarlyup
2026-08-1044MediumEarlyup
2026-08-0944MediumEarlyup
2026-08-0844MediumEarlyup
2026-08-0744MediumEarlyup
2026-08-0642MediumEarlyup
2026-08-0542MediumEarlyup
2026-08-0442MediumEarlyup
2026-08-0342MediumEarlyup
2026-08-0242MediumEarlyup
2026-08-0142MediumEarlyup
2026-07-3142MediumEarlyup
2026-07-3042MediumEarlyup
2026-07-2942MediumEarlyup
2026-07-2842MediumEarlyup
2026-07-2742MediumEarlyup
2026-07-2642MediumEarlyup
2026-07-2542MediumEarlyup
2026-07-2442MediumEarlyup
2026-07-2342MediumEarlyup
2026-07-2242MediumEarlyup
2026-07-2142MediumEarlyup
2026-07-2042MediumEarlyup
2026-07-1941MediumEarlyup

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. Sep 8, 2026
    Sato Score tier: Low → Medium
    Score 32 → 46.
  2. Sep 7, 2026
    Sato Score tier: Medium → Low
    Score 47 → 32.
  3. Aug 7, 2026
    Auto-enriched: supported integrations
  4. Jul 20, 2026
    Edited: deploy spec
  5. Jul 19, 2026
    Listed on Sato Hub
  6. Jul 19, 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