Score history

SODAX Builders MCP

Name: SODAX Builders 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

+19

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-06	78	83	+5	the project
2026-09-18	69	78	+9	the project
2026-09-17	79	69	-10	the project
2026-09-01	76	79	+3	Sato Hub changed the scoring method
2026-07-21	75	76	+1	the project
2026-07-20	64	75	+11	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 verifiability10/10

Docs & demo6/10

Listing transparency & provenance13/15

Independent verification2/10

The observed record

98.1% 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	83	High	Active	up
2026-10-28	83	High	Active	up
2026-10-27	83	High	Active	up
2026-10-26	83	High	Active	up
2026-10-25	83	High	Active	up
2026-10-24	83	High	Active	up
2026-10-23	83	High	Active	up
2026-10-22	83	High	Active	up
2026-10-21	83	High	Active	up
2026-10-20	83	High	Active	up
2026-10-19	83	High	Active	up
2026-10-18	83	High	Active	up
2026-10-17	83	High	Active	up
2026-10-16	83	High	Active	up
2026-10-15	83	High	Active	up
2026-10-14	83	High	Active	up
2026-10-13	83	High	Active	up
2026-10-12	83	High	Active	up
2026-10-11	83	High	Active	up
2026-10-10	83	High	Active	up
2026-10-09	83	High	Active	up
2026-10-08	83	High	Active	up
2026-10-07	83	High	Active	up
2026-10-06	83	High	Active	up
2026-10-05	78	High	Active	up
2026-10-04	78	High	Active	inconclusive
2026-10-03	78	High	Active	up
2026-10-02	78	High	Active	up
2026-10-01	78	High	Active	up
2026-09-30	78	High	Active	up
2026-09-29	78	High	Active	up
2026-09-28	78	High	Active	up
2026-09-27	78	High	Active	up
2026-09-26	78	High	Active	up
2026-09-25	78	High	Active	up
2026-09-24	78	High	Active	up
2026-09-23	78	High	Active	up
2026-09-22	78	High	Active	up
2026-09-21	78	High	Active	up
2026-09-20	78	High	Active	up
2026-09-19	78	High	Active	up
2026-09-18	78	High	Active	up
2026-09-17	69	Medium	Active	inconclusive
2026-09-16	79	High	Active	up
2026-09-15	79	High	Active	up
2026-09-14	79	High	Active	up
2026-09-13	79	High	Active	up
2026-09-12	79	High	Active	up
2026-09-11	79	High	Active	up
2026-09-10	79	High	Active	up
2026-09-09	79	High	Active	up
2026-09-08	79	High	Active	up
2026-09-07	79	High	Active	up
2026-09-06	79	High	Active	up
2026-09-05	79	High	Active	up
2026-09-04	79	High	Active	up
2026-09-03	79	High	Active	up
2026-09-02	79	High	Active	up
2026-09-01	79	High	Active	up
2026-08-31	76	High	Active	up
2026-08-30	76	High	Active	up
2026-08-29	76	High	Active	up
2026-08-28	76	High	Active	up
2026-08-27	76	High	Active	up
2026-08-26	76	High	Active	up
2026-08-25	76	High	Active	up
2026-08-24	76	High	Active	up
2026-08-23	76	High	Active	up
2026-08-22	76	High	Active	up
2026-08-21	76	High	Active	up
2026-08-20	76	High	Active	up
2026-08-19	76	High	Active	up
2026-08-18	76	High	Active	up
2026-08-17	76	High	Active	up
2026-08-16	76	High	Active	up
2026-08-15	76	High	Active	up
2026-08-14	76	High	Active	up
2026-08-13	76	High	Active	up
2026-08-12	76	High	Active	up
2026-08-11	76	High	Active	up
2026-08-10	76	High	Active	up
2026-08-09	76	High	Active	up
2026-08-08	76	High	Active	up
2026-08-07	76	High	Active	up
2026-08-06	76	High	Active	up
2026-08-05	76	High	Active	up
2026-08-04	76	High	Active	up
2026-08-03	76	High	Active	up
2026-08-02	76	High	Active	up
2026-08-01	76	High	Active	up
2026-07-31	76	High	Active	up
2026-07-30	76	High	Active	up
2026-07-29	76	High	Active	up
2026-07-28	76	High	Active	up
2026-07-27	76	High	Active	up
2026-07-26	76	High	Active	up
2026-07-25	76	High	Active	up
2026-07-24	76	High	Active	up
2026-07-23	76	High	Active	up
2026-07-22	76	High	Active	up
2026-07-21	76	High	Active	up
2026-07-20	75	High	Active	up
2026-07-19	64	Medium	Active	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 26, 2026
Verified: deploy spec
Oct 6, 2026
Auto-enriched: deployment options, supported integrations, tags
Sep 18, 2026
Sato Score tier: Medium → High
Score 69 → 78.
Sep 17, 2026
Sato Score tier: High → Medium
Score 79 → 69.
Aug 3, 2026
New release published
Jul 31, 2026
Sato Hub began tracking this listing
Jul 20, 2026
Edited: mcp endpoint url
Jul 19, 2026
Edited: description long
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