Score history

Usenami Signer MCP

Name: Usenami Signer MCP — Sato Score daily history
Creator: Sato Hub
License: https://creativecommons.org/licenses/by/4.0/

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

Change over 103d

+23

Days measured

103

Days missed

Sato Score, daily

2026-07-19 → 2026-10-29

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

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

Date	From	To	Change	Cause
2026-10-20	61	69	+8	the project
2026-09-13	51	61	+10	the project
2026-09-06	61	51	-10	the project
2026-09-01	58	61	+3	Sato Hub changed the scoring method
2026-08-10	47	58	+11	the project
2026-07-20	46	47	+1	Sato 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

Code transparency17/20

Interface verifiability8/10

Docs & demo0/10

Listing transparency & provenance6/15

Independent verification3/10

The observed record

100% of 103 daily checks since 2026-07-19 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

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.

Date	Score	Tier	Status	Our check
2026-10-29	69	Medium	Early	up
2026-10-28	69	Medium	Early	up
2026-10-27	69	Medium	Early	up
2026-10-26	69	Medium	Early	up
2026-10-25	69	Medium	Early	up
2026-10-24	69	Medium	Early	up
2026-10-23	69	Medium	Early	up
2026-10-22	69	Medium	Early	up
2026-10-21	69	Medium	Early	up
2026-10-20	69	Medium	Early	up
2026-10-19	61	Medium	Early	up
2026-10-18	61	Medium	Early	up
2026-10-17	61	Medium	Early	up
2026-10-16	61	Medium	Early	up
2026-10-15	61	Medium	Early	up
2026-10-14	61	Medium	Early	up
2026-10-13	61	Medium	Early	up
2026-10-12	61	Medium	Early	up
2026-10-11	61	Medium	Early	up
2026-10-10	61	Medium	Early	up
2026-10-09	61	Medium	Early	up
2026-10-08	61	Medium	Early	up
2026-10-07	61	Medium	Early	up
2026-10-06	61	Medium	Early	up
2026-10-05	61	Medium	Early	up
2026-10-04	61	Medium	Early	up
2026-10-03	61	Medium	Early	up
2026-10-02	61	Medium	Early	up
2026-10-01	61	Medium	Early	up
2026-09-30	61	Medium	Early	up
2026-09-29	61	Medium	Early	up
2026-09-28	61	Medium	Early	up
2026-09-27	61	Medium	Early	up
2026-09-26	61	Medium	Early	up
2026-09-25	61	Medium	Early	up
2026-09-24	61	Medium	Early	up
2026-09-23	61	Medium	Early	up
2026-09-22	61	Medium	Early	up
2026-09-21	61	Medium	Early	up
2026-09-20	61	Medium	Early	up
2026-09-19	61	Medium	Early	up
2026-09-18	61	Medium	Early	up
2026-09-17	61	Medium	Early	up
2026-09-16	61	Medium	Early	up
2026-09-15	61	Medium	Early	up
2026-09-14	61	Medium	Early	up
2026-09-13	61	Medium	Early	up
2026-09-12	51	Medium	Early	up
2026-09-11	51	Medium	Early	up
2026-09-10	51	Medium	Early	up
2026-09-09	51	Medium	Early	up
2026-09-08	51	Medium	Early	up
2026-09-07	51	Medium	Early	up
2026-09-06	51	Medium	Early	up
2026-09-05	61	Medium	Early	up
2026-09-04	61	Medium	Early	up
2026-09-03	61	Medium	Early	up
2026-09-02	61	Medium	Early	up
2026-09-01	61	Medium	Early	up
2026-08-31	58	Medium	Early	up
2026-08-30	58	Medium	Early	up
2026-08-29	58	Medium	Early	up
2026-08-28	58	Medium	Early	up
2026-08-27	58	Medium	Early	up
2026-08-26	58	Medium	Early	up
2026-08-25	58	Medium	Early	up
2026-08-24	58	Medium	Early	up
2026-08-23	58	Medium	Early	up
2026-08-22	58	Medium	Early	up
2026-08-21	58	Medium	Early	up
2026-08-20	58	Medium	Early	up
2026-08-19	58	Medium	Early	up
2026-08-18	58	Medium	Early	up
2026-08-17	58	Medium	Early	up
2026-08-16	58	Medium	Early	up
2026-08-15	58	Medium	Early	up
2026-08-14	58	Medium	Early	up
2026-08-13	58	Medium	Early	up
2026-08-12	58	Medium	Early	up
2026-08-11	58	Medium	Early	up
2026-08-10	58	Medium	Early	up
2026-08-09	47	Medium	Early	up
2026-08-08	47	Medium	Early	up
2026-08-07	47	Medium	Early	up
2026-08-06	47	Medium	Early	up
2026-08-05	47	Medium	Early	up
2026-08-04	47	Medium	Early	up
2026-08-03	47	Medium	Early	up
2026-08-02	47	Medium	Early	up
2026-08-01	47	Medium	Early	up
2026-07-31	47	Medium	Early	up
2026-07-30	47	Medium	Early	up
2026-07-29	47	Medium	Early	up
2026-07-28	47	Medium	Early	up
2026-07-27	47	Medium	Early	up
2026-07-26	47	Medium	Early	up
2026-07-25	47	Medium	Early	up
2026-07-24	47	Medium	Early	up
2026-07-23	47	Medium	Early	up
2026-07-22	47	Medium	Early	up
2026-07-21	47	Medium	Early	up
2026-07-20	47	Medium	Early	up
2026-07-19	46	Medium	Early	up

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.

Oct 19, 2026
Verified: deploy spec
Sep 26, 2026
Edited: entity class, resource type
Aug 1, 2026
Sato Hub began tracking this listing
Jul 19, 2026
Listed on Sato Hub

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 record This week’s movers Dispute this score