Sato Hub
Usenami Signer MCP verification record

Score history

Usenami Signer 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

61

Change over 57d

+15

Days measured

57

Days missed

0

Sato Score, daily

2026-07-192026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (46 → 47). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (58 → 61). Not a change by the project.2026-07-19: 46 (Medium)2026-07-20: 47 (Medium)2026-07-21: 47 (Medium)2026-07-22: 47 (Medium)2026-07-23: 47 (Medium)2026-07-24: 47 (Medium)2026-07-25: 47 (Medium)2026-07-26: 47 (Medium)2026-07-27: 47 (Medium)2026-07-28: 47 (Medium)2026-07-29: 47 (Medium)2026-07-30: 47 (Medium)2026-07-31: 47 (Medium)2026-08-01: 47 (Medium)2026-08-02: 47 (Medium)2026-08-03: 47 (Medium)2026-08-04: 47 (Medium)2026-08-05: 47 (Medium)2026-08-06: 47 (Medium)2026-08-07: 47 (Medium)2026-08-08: 47 (Medium)2026-08-09: 47 (Medium)2026-08-10: 58 (Medium)2026-08-11: 58 (Medium)2026-08-12: 58 (Medium)2026-08-13: 58 (Medium)2026-08-14: 58 (Medium)2026-08-15: 58 (Medium)2026-08-16: 58 (Medium)2026-08-17: 58 (Medium)2026-08-18: 58 (Medium)2026-08-19: 58 (Medium)2026-08-20: 58 (Medium)2026-08-21: 58 (Medium)2026-08-22: 58 (Medium)2026-08-23: 58 (Medium)2026-08-24: 58 (Medium)2026-08-25: 58 (Medium)2026-08-26: 58 (Medium)2026-08-27: 58 (Medium)2026-08-28: 58 (Medium)2026-08-29: 58 (Medium)2026-08-30: 58 (Medium)2026-08-31: 58 (Medium)2026-09-01: 61 (Medium)2026-09-02: 61 (Medium)2026-09-03: 61 (Medium)2026-09-04: 61 (Medium)2026-09-05: 61 (Medium)2026-09-06: 51 (Medium)2026-09-07: 51 (Medium)2026-09-08: 51 (Medium)2026-09-09: 51 (Medium)2026-09-10: 51 (Medium)2026-09-11: 51 (Medium)2026-09-12: 51 (Medium)2026-09-13: 61 (Medium)4661612026-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-135161+10the project
2026-09-066151-10the project
2026-09-015861+3Sato Hub changed the scoring method
2026-08-104758+11the project
2026-07-204647+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 & liveness35/35
35
Code transparency17/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance6/15
15
Independent verification3/10
10

The observed record

100% 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: 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-1361MediumEarlyup
2026-09-1251MediumEarlyup
2026-09-1151MediumEarlyup
2026-09-1051MediumEarlyup
2026-09-0951MediumEarlyup
2026-09-0851MediumEarlyup
2026-09-0751MediumEarlyup
2026-09-0651MediumEarlyup
2026-09-0561MediumEarlyup
2026-09-0461MediumEarlyup
2026-09-0361MediumEarlyup
2026-09-0261MediumEarlyup
2026-09-0161MediumEarlyup
2026-08-3158MediumEarlyup
2026-08-3058MediumEarlyup
2026-08-2958MediumEarlyup
2026-08-2858MediumEarlyup
2026-08-2758MediumEarlyup
2026-08-2658MediumEarlyup
2026-08-2558MediumEarlyup
2026-08-2458MediumEarlyup
2026-08-2358MediumEarlyup
2026-08-2258MediumEarlyup
2026-08-2158MediumEarlyup
2026-08-2058MediumEarlyup
2026-08-1958MediumEarlyup
2026-08-1858MediumEarlyup
2026-08-1758MediumEarlyup
2026-08-1658MediumEarlyup
2026-08-1558MediumEarlyup
2026-08-1458MediumEarlyup
2026-08-1358MediumEarlyup
2026-08-1258MediumEarlyup
2026-08-1158MediumEarlyup
2026-08-1058MediumEarlyup
2026-08-0947MediumEarlyup
2026-08-0847MediumEarlyup
2026-08-0747MediumEarlyup
2026-08-0647MediumEarlyup
2026-08-0547MediumEarlyup
2026-08-0447MediumEarlyup
2026-08-0347MediumEarlyup
2026-08-0247MediumEarlyup
2026-08-0147MediumEarlyup
2026-07-3147MediumEarlyup
2026-07-3047MediumEarlyup
2026-07-2947MediumEarlyup
2026-07-2847MediumEarlyup
2026-07-2747MediumEarlyup
2026-07-2647MediumEarlyup
2026-07-2547MediumEarlyup
2026-07-2447MediumEarlyup
2026-07-2347MediumEarlyup
2026-07-2247MediumEarlyup
2026-07-2147MediumEarlyup
2026-07-2047MediumEarlyup
2026-07-1946MediumEarlyup

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: deploy spec
  2. Jul 19, 2026
    Listed on Sato Hub
  3. 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.