Score history

Lighter MCP

Name: Lighter 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

+15

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

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

Date	From	To	Change	Cause
2026-09-01	53	56	+3	Sato Hub changed the scoring method
2026-08-27	58	53	-5	the project
2026-08-09	52	58	+6	the project
2026-08-05	50	52	+2	the project
2026-07-20	41	50	+9	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 & liveness20/35

Code transparency17/20

Interface verifiability8/10

Docs & demo0/10

Listing transparency & provenance8/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	56	Medium	Early	up
2026-10-28	56	Medium	Early	up
2026-10-27	56	Medium	Early	up
2026-10-26	56	Medium	Early	up
2026-10-25	56	Medium	Early	up
2026-10-24	56	Medium	Early	up
2026-10-23	56	Medium	Early	up
2026-10-22	56	Medium	Early	up
2026-10-21	56	Medium	Early	up
2026-10-20	56	Medium	Early	up
2026-10-19	56	Medium	Early	up
2026-10-18	56	Medium	Early	up
2026-10-17	56	Medium	Early	up
2026-10-16	56	Medium	Early	up
2026-10-15	56	Medium	Early	up
2026-10-14	56	Medium	Early	up
2026-10-13	56	Medium	Early	up
2026-10-12	56	Medium	Early	up
2026-10-11	56	Medium	Early	up
2026-10-10	56	Medium	Early	up
2026-10-09	56	Medium	Early	up
2026-10-08	56	Medium	Early	up
2026-10-07	56	Medium	Early	up
2026-10-06	56	Medium	Early	up
2026-10-05	56	Medium	Early	up
2026-10-04	56	Medium	Early	up
2026-10-03	56	Medium	Early	up
2026-10-02	56	Medium	Early	up
2026-10-01	56	Medium	Early	up
2026-09-30	56	Medium	Early	up
2026-09-29	56	Medium	Early	up
2026-09-28	56	Medium	Early	up
2026-09-27	56	Medium	Early	up
2026-09-26	56	Medium	Early	up
2026-09-25	56	Medium	Early	up
2026-09-24	56	Medium	Early	up
2026-09-23	56	Medium	Early	up
2026-09-22	56	Medium	Early	up
2026-09-21	56	Medium	Early	up
2026-09-20	56	Medium	Early	up
2026-09-19	56	Medium	Early	up
2026-09-18	56	Medium	Early	up
2026-09-17	56	Medium	Early	up
2026-09-16	56	Medium	Early	up
2026-09-15	56	Medium	Early	up
2026-09-14	56	Medium	Early	up
2026-09-13	56	Medium	Early	up
2026-09-12	56	Medium	Early	up
2026-09-11	56	Medium	Early	up
2026-09-10	56	Medium	Early	up
2026-09-09	56	Medium	Early	up
2026-09-08	56	Medium	Early	up
2026-09-07	56	Medium	Early	up
2026-09-06	56	Medium	Early	up
2026-09-05	56	Medium	Early	up
2026-09-04	56	Medium	Early	up
2026-09-03	56	Medium	Early	up
2026-09-02	56	Medium	Early	up
2026-09-01	56	Medium	Early	up
2026-08-31	53	Medium	Early	up
2026-08-30	53	Medium	Early	up
2026-08-29	53	Medium	Early	up
2026-08-28	53	Medium	Early	up
2026-08-27	53	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	58	Medium	Early	up
2026-08-08	52	Medium	Early	up
2026-08-07	52	Medium	Early	up
2026-08-06	52	Medium	Early	up
2026-08-05	52	Medium	Early	up
2026-08-04	50	Medium	Early	up
2026-08-03	50	Medium	Early	up
2026-08-02	50	Medium	Early	up
2026-08-01	50	Medium	Early	up
2026-07-31	50	Medium	Early	up
2026-07-30	50	Medium	Early	up
2026-07-29	50	Medium	Early	up
2026-07-28	50	Medium	Early	up
2026-07-27	50	Medium	Early	up
2026-07-26	50	Medium	Early	up
2026-07-25	50	Medium	Early	up
2026-07-24	50	Medium	Early	up
2026-07-23	50	Medium	Early	up
2026-07-22	50	Medium	Early	up
2026-07-21	50	Medium	Early	up
2026-07-20	50	Medium	Early	up
2026-07-19	41	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.

Sep 26, 2026
Edited: entity class, resource type
Aug 5, 2026
Auto-enriched: supported integrations
Aug 1, 2026
Sato Hub began tracking this listing
Jul 21, 2026
Verified: deploy spec
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