Score history

AIBTC MCP Server

Name: AIBTC MCP Server — 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 108d

+12

Days measured

108

Days missed

Sato Score, daily

2026-07-14 → 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

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

Date	From	To	Change	Cause
2026-09-01	79	82	+3	Sato Hub changed the scoring method
2026-07-20	71	79	+8	Sato Hub changed the scoring method
2026-07-15	70	71	+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 transparency18/20

Interface verifiability8/10

Docs & demo6/10

Listing transparency & provenance12/15

Independent verification3/10

The observed record

100% 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	82	High	Active	up
2026-10-28	82	High	Active	up
2026-10-27	82	High	Active	up
2026-10-26	82	High	Active	up
2026-10-25	82	High	Active	up
2026-10-24	82	High	Active	up
2026-10-23	82	High	Active	up
2026-10-22	82	High	Active	up
2026-10-21	82	High	Active	up
2026-10-20	82	High	Active	up
2026-10-19	82	High	Active	up
2026-10-18	82	High	Active	up
2026-10-17	82	High	Active	up
2026-10-16	82	High	Active	up
2026-10-15	82	High	Active	up
2026-10-14	82	High	Active	up
2026-10-13	82	High	Active	up
2026-10-12	82	High	Active	up
2026-10-11	82	High	Active	up
2026-10-10	82	High	Active	up
2026-10-09	82	High	Active	up
2026-10-08	82	High	Active	up
2026-10-07	82	High	Active	up
2026-10-06	82	High	Active	up
2026-10-05	82	High	Active	up
2026-10-04	82	High	Active	up
2026-10-03	82	High	Active	up
2026-10-02	82	High	Active	up
2026-10-01	82	High	Active	up
2026-09-30	82	High	Active	up
2026-09-29	82	High	Active	up
2026-09-28	82	High	Active	up
2026-09-27	82	High	Active	up
2026-09-26	82	High	Active	up
2026-09-25	82	High	Active	up
2026-09-24	82	High	Active	up
2026-09-23	82	High	Active	up
2026-09-22	82	High	Active	up
2026-09-21	82	High	Active	up
2026-09-20	82	High	Active	up
2026-09-19	82	High	Active	up
2026-09-18	82	High	Active	up
2026-09-17	82	High	Active	up
2026-09-16	82	High	Active	up
2026-09-15	82	High	Active	up
2026-09-14	82	High	Active	up
2026-09-13	82	High	Active	up
2026-09-12	82	High	Active	up
2026-09-11	82	High	Active	up
2026-09-10	82	High	Active	up
2026-09-09	82	High	Active	up
2026-09-08	82	High	Active	up
2026-09-07	82	High	Active	up
2026-09-06	82	High	Active	up
2026-09-05	82	High	Active	up
2026-09-04	82	High	Active	up
2026-09-03	82	High	Active	up
2026-09-02	82	High	Active	up
2026-09-01	82	High	Active	up
2026-08-31	79	High	Active	up
2026-08-30	79	High	Active	up
2026-08-29	79	High	Active	up
2026-08-28	79	High	Active	up
2026-08-27	79	High	Active	up
2026-08-26	79	High	Active	up
2026-08-25	79	High	Active	up
2026-08-24	79	High	Active	up
2026-08-23	79	High	Active	up
2026-08-22	79	High	Active	up
2026-08-21	79	High	Active	up
2026-08-20	79	High	Active	up
2026-08-19	79	High	Active	up
2026-08-18	79	High	Active	up
2026-08-17	79	High	Active	up
2026-08-16	79	High	Active	up
2026-08-15	79	High	Active	up
2026-08-14	79	High	Active	up
2026-08-13	79	High	Active	up
2026-08-12	79	High	Active	up
2026-08-11	79	High	Active	up
2026-08-10	79	High	Active	up
2026-08-09	79	High	Active	up
2026-08-08	79	High	Active	up
2026-08-07	79	High	Active	up
2026-08-06	79	High	Active	up
2026-08-05	79	High	Active	up
2026-08-04	79	High	Active	up
2026-08-03	79	High	Active	up
2026-08-02	79	High	Active	up
2026-08-01	79	High	Active	up
2026-07-31	79	High	Active	up
2026-07-30	79	High	Active	up
2026-07-29	79	High	Active	up
2026-07-28	79	High	Active	up
2026-07-27	79	High	Active	up
2026-07-26	79	High	Active	up
2026-07-25	79	High	Active	up
2026-07-24	79	High	Active	up
2026-07-23	79	High	Active	up
2026-07-22	79	High	Active	up
2026-07-21	79	High	Active	up
2026-07-20	79	High	Active	up
2026-07-19	71	High	Active	up
2026-07-18	71	High	Active	up
2026-07-17	71	High	Active	up
2026-07-16	71	High	Active	up
2026-07-15	71	High	Active	up
2026-07-14	70	High	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 27, 2026
New release published
Oct 26, 2026
New release published
Sep 21, 2026
Verified: deploy spec
Aug 3, 2026
13 releases tracked
Showing the 2 most recent. Full release history is retained in the listing record.
Aug 1, 2026
Sato Hub began tracking this listing
Jul 14, 2026
Auto-enriched: deployment options, supported integrations
Jul 14, 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