Score history

MCP Reference Servers

Name: MCP Reference Servers — 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 109d

Days measured

109

Days missed

Sato Score, daily

2026-07-13 → 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, 4 caused by a revision of the scoring method.

Date	From	To	Change	Cause
2026-09-22	73	72	-1	the project
2026-09-01	70	73	+3	Sato Hub changed the scoring method
2026-07-20	62	70	+8	Sato Hub changed the scoring method
2026-07-19	72	62	-10	the project
2026-07-18	62	72	+10	the project
2026-07-15	61	62	+1	Sato Hub changed the scoring method
2026-07-14	66	61	-5	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 transparency20/20

Interface verifiability8/10

Docs & demo0/10

Listing transparency & provenance7/15

Independent verification2/10

The observed record

99.1% of 108 daily checks since 2026-07-14 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	72	High	Active	up
2026-10-28	72	High	Active	up
2026-10-27	72	High	Active	up
2026-10-26	72	High	Active	up
2026-10-25	72	High	Active	up
2026-10-24	72	High	Active	up
2026-10-23	72	High	Active	up
2026-10-22	72	High	Active	up
2026-10-21	72	High	Active	up
2026-10-20	72	High	Active	up
2026-10-19	72	High	Active	up
2026-10-18	72	High	Active	up
2026-10-17	72	High	Active	up
2026-10-16	72	High	Active	up
2026-10-15	72	High	Active	up
2026-10-14	72	High	Active	up
2026-10-13	72	High	Active	up
2026-10-12	72	High	Active	up
2026-10-11	72	High	Active	up
2026-10-10	72	High	Active	up
2026-10-09	72	High	Active	up
2026-10-08	72	High	Active	up
2026-10-07	72	High	Active	up
2026-10-06	72	High	Active	up
2026-10-05	72	High	Active	up
2026-10-04	72	High	Active	up
2026-10-03	72	High	Active	up
2026-10-02	72	High	Active	up
2026-10-01	72	High	Active	up
2026-09-30	72	High	Active	up
2026-09-29	72	High	Active	up
2026-09-28	72	High	Active	up
2026-09-27	72	High	Active	up
2026-09-26	72	High	Active	up
2026-09-25	72	High	Active	up
2026-09-24	72	High	Active	up
2026-09-23	72	High	Active	up
2026-09-22	72	High	Active	up
2026-09-21	73	High	Active	inconclusive
2026-09-20	73	High	Active	up
2026-09-19	73	High	Active	up
2026-09-18	73	High	Active	up
2026-09-17	73	High	Active	up
2026-09-16	73	High	Active	up
2026-09-15	73	High	Active	up
2026-09-14	73	High	Active	up
2026-09-13	73	High	Active	up
2026-09-12	73	High	Active	up
2026-09-11	73	High	Active	up
2026-09-10	73	High	Active	up
2026-09-09	73	High	Active	up
2026-09-08	73	High	Active	up
2026-09-07	73	High	Active	up
2026-09-06	73	High	Active	up
2026-09-05	73	High	Active	up
2026-09-04	73	High	Active	up
2026-09-03	73	High	Active	up
2026-09-02	73	High	Active	up
2026-09-01	73	High	Active	up
2026-08-31	70	High	Active	up
2026-08-30	70	High	Active	up
2026-08-29	70	High	Active	up
2026-08-28	70	High	Active	up
2026-08-27	70	High	Active	up
2026-08-26	70	High	Active	up
2026-08-25	70	High	Active	up
2026-08-24	70	High	Active	up
2026-08-23	70	High	Active	up
2026-08-22	70	High	Active	up
2026-08-21	70	High	Active	up
2026-08-20	70	High	Active	up
2026-08-19	70	High	Active	up
2026-08-18	70	High	Active	up
2026-08-17	70	High	Active	up
2026-08-16	70	High	Active	up
2026-08-15	70	High	Active	up
2026-08-14	70	High	Active	up
2026-08-13	70	High	Active	up
2026-08-12	70	High	Active	up
2026-08-11	70	High	Active	up
2026-08-10	70	High	Active	up
2026-08-09	70	High	Active	up
2026-08-08	70	High	Active	up
2026-08-07	70	High	Active	up
2026-08-06	70	High	Active	up
2026-08-05	70	High	Active	up
2026-08-04	70	High	Active	up
2026-08-03	70	High	Active	up
2026-08-02	70	High	Active	up
2026-08-01	70	High	Active	up
2026-07-31	70	High	Active	up
2026-07-30	70	High	Active	up
2026-07-29	70	High	Active	up
2026-07-28	70	High	Active	up
2026-07-27	70	High	Active	up
2026-07-26	70	High	Active	up
2026-07-25	70	High	Active	up
2026-07-24	70	High	Active	up
2026-07-23	70	High	Active	up
2026-07-22	70	High	Active	up
2026-07-21	70	High	Active	up
2026-07-20	70	High	Active	up
2026-07-19	62	Medium	Active	up
2026-07-18	72	High	Active	up
2026-07-17	62	Medium	Active	up
2026-07-16	62	Medium	Active	up
2026-07-15	62	Medium	Active	up
2026-07-14	61	Medium	Active	up
2026-07-13	66	Medium	Active	not 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.

Oct 25, 2026
New release published
Oct 19, 2026
New release published
Aug 18, 2026
5 releases tracked
Showing the 2 most recent. Full release history is retained in the listing record.
Jul 31, 2026
Sato Hub began tracking this listing
Jul 21, 2026
Verified: deploy spec
Jul 18, 2026
Auto-enriched: docs url, deployment options
Jul 13, 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