Score history

Circle Agent Stack MCP

Name: Circle Agent Stack 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

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

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

Date	From	To	Change	Cause
2026-09-03	57	52	-5	the project
2026-09-01	54	57	+3	Sato Hub changed the scoring method
2026-07-28	53	54	+1	the project
2026-07-20	50	53	+3	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 transparency13/20

Interface verifiability8/10

Docs & demo0/10

Listing transparency & provenance6/15

Independent verification5/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	52	Medium	Early	up
2026-10-28	52	Medium	Early	up
2026-10-27	52	Medium	Early	up
2026-10-26	52	Medium	Early	up
2026-10-25	52	Medium	Early	up
2026-10-24	52	Medium	Early	up
2026-10-23	52	Medium	Early	up
2026-10-22	52	Medium	Early	up
2026-10-21	52	Medium	Early	up
2026-10-20	52	Medium	Early	up
2026-10-19	52	Medium	Early	up
2026-10-18	52	Medium	Early	up
2026-10-17	52	Medium	Early	up
2026-10-16	52	Medium	Early	up
2026-10-15	52	Medium	Early	up
2026-10-14	52	Medium	Early	up
2026-10-13	52	Medium	Early	up
2026-10-12	52	Medium	Early	up
2026-10-11	52	Medium	Early	up
2026-10-10	52	Medium	Early	up
2026-10-09	52	Medium	Early	up
2026-10-08	52	Medium	Early	up
2026-10-07	52	Medium	Early	up
2026-10-06	52	Medium	Early	up
2026-10-05	52	Medium	Early	up
2026-10-04	52	Medium	Early	up
2026-10-03	52	Medium	Early	up
2026-10-02	52	Medium	Early	up
2026-10-01	52	Medium	Early	up
2026-09-30	52	Medium	Early	up
2026-09-29	52	Medium	Early	up
2026-09-28	52	Medium	Early	up
2026-09-27	52	Medium	Early	up
2026-09-26	52	Medium	Early	up
2026-09-25	52	Medium	Early	up
2026-09-24	52	Medium	Early	up
2026-09-23	52	Medium	Early	up
2026-09-22	52	Medium	Early	up
2026-09-21	52	Medium	Early	up
2026-09-20	52	Medium	Early	up
2026-09-19	52	Medium	Early	up
2026-09-18	52	Medium	Early	up
2026-09-17	52	Medium	Early	up
2026-09-16	52	Medium	Early	up
2026-09-15	52	Medium	Early	up
2026-09-14	52	Medium	Early	up
2026-09-13	52	Medium	Early	up
2026-09-12	52	Medium	Early	up
2026-09-11	52	Medium	Early	up
2026-09-10	52	Medium	Early	up
2026-09-09	52	Medium	Early	up
2026-09-08	52	Medium	Early	up
2026-09-07	52	Medium	Early	up
2026-09-06	52	Medium	Early	up
2026-09-05	52	Medium	Early	up
2026-09-04	52	Medium	Early	up
2026-09-03	52	Medium	Early	up
2026-09-02	57	Medium	Early	up
2026-09-01	57	Medium	Early	up
2026-08-31	54	Medium	Early	up
2026-08-30	54	Medium	Early	up
2026-08-29	54	Medium	Early	up
2026-08-28	54	Medium	Early	up
2026-08-27	54	Medium	Early	up
2026-08-26	54	Medium	Early	up
2026-08-25	54	Medium	Early	up
2026-08-24	54	Medium	Early	up
2026-08-23	54	Medium	Early	up
2026-08-22	54	Medium	Early	up
2026-08-21	54	Medium	Early	up
2026-08-20	54	Medium	Early	up
2026-08-19	54	Medium	Early	up
2026-08-18	54	Medium	Early	up
2026-08-17	54	Medium	Early	up
2026-08-16	54	Medium	Early	up
2026-08-15	54	Medium	Early	up
2026-08-14	54	Medium	Early	up
2026-08-13	54	Medium	Early	up
2026-08-12	54	Medium	Early	up
2026-08-11	54	Medium	Early	up
2026-08-10	54	Medium	Early	up
2026-08-09	54	Medium	Early	up
2026-08-08	54	Medium	Early	up
2026-08-07	54	Medium	Early	up
2026-08-06	54	Medium	Early	up
2026-08-05	54	Medium	Early	up
2026-08-04	54	Medium	Early	up
2026-08-03	54	Medium	Early	up
2026-08-02	54	Medium	Early	up
2026-08-01	54	Medium	Early	up
2026-07-31	54	Medium	Early	up
2026-07-30	54	Medium	Early	up
2026-07-29	54	Medium	Early	up
2026-07-28	54	Medium	Early	up
2026-07-27	53	Medium	Early	up
2026-07-26	53	Medium	Early	up
2026-07-25	53	Medium	Early	up
2026-07-24	53	Medium	Early	up
2026-07-23	53	Medium	Early	up
2026-07-22	53	Medium	Early	up
2026-07-21	53	Medium	Early	up
2026-07-20	53	Medium	Early	up
2026-07-19	50	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 26, 2026
Verified: deploy spec
Aug 1, 2026
Sato Hub began tracking this listing
Jul 19, 2026
Edited: website url
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