Score history

PaladinFi Swap MCP

Name: PaladinFi Swap 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

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

Date	From	To	Change	Cause
2026-10-10	50	52	+2	Sato Hub changed the scoring method
2026-09-11	42	50	+8	the project
2026-09-04	35	42	+7	the project
2026-09-03	42	35	-7	the project
2026-08-29	35	42	+7	the project
2026-08-27	42	35	-7	the project
2026-08-22	47	42	-5	the project
2026-07-20	46	47	+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 & liveness20/35

Code transparency16/20

Interface verifiability0/10

Docs & demo4/10

Listing transparency & provenance10/15

Independent verification2/10

The observed record

98.3% of 59 daily checks since 2026-09-01 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	50	Medium	Early	up
2026-10-08	50	Medium	Early	up
2026-10-07	50	Medium	Early	up
2026-10-06	50	Medium	Early	up
2026-10-05	50	Medium	Early	up
2026-10-04	50	Medium	Early	up
2026-10-03	50	Medium	Early	up
2026-10-02	50	Medium	Early	up
2026-10-01	50	Medium	Early	up
2026-09-30	50	Medium	Early	up
2026-09-29	50	Medium	Early	up
2026-09-28	50	Medium	Early	up
2026-09-27	50	Medium	Early	up
2026-09-26	50	Medium	Early	up
2026-09-25	50	Medium	Early	up
2026-09-24	50	Medium	Early	up
2026-09-23	50	Medium	Early	up
2026-09-22	50	Medium	Early	up
2026-09-21	50	Medium	Early	up
2026-09-20	50	Medium	Early	up
2026-09-19	50	Medium	Early	up
2026-09-18	50	Medium	Early	up
2026-09-17	50	Medium	Early	up
2026-09-16	50	Medium	Early	up
2026-09-15	50	Medium	Early	up
2026-09-14	50	Medium	Early	up
2026-09-13	50	Medium	Early	up
2026-09-12	50	Medium	Early	up
2026-09-11	50	Medium	Early	up
2026-09-10	42	Medium	Early	up
2026-09-09	42	Medium	Early	up
2026-09-08	42	Medium	Early	up
2026-09-07	42	Medium	Early	up
2026-09-06	42	Medium	Early	up
2026-09-05	42	Medium	Early	up
2026-09-04	42	Medium	Early	up
2026-09-03	35	Low	Early	inconclusive
2026-09-02	42	Medium	Early	up
2026-09-01	42	Medium	Early	up
2026-08-31	42	Medium	Early	up
2026-08-30	42	Medium	Early	up
2026-08-29	42	Medium	Early	up
2026-08-28	35	Low	Early	unknown
2026-08-27	35	Low	Early	unknown
2026-08-26	42	Medium	Early	up
2026-08-25	42	Medium	Early	up
2026-08-24	42	Medium	Early	up
2026-08-23	42	Medium	Early	up
2026-08-22	42	Medium	Early	up
2026-08-21	47	Medium	Early	unknown
2026-08-20	47	Medium	Early	up
2026-08-19	47	Medium	Early	up
2026-08-18	47	Medium	Early	up
2026-08-17	47	Medium	Early	unknown
2026-08-16	47	Medium	Early	up
2026-08-15	47	Medium	Early	up
2026-08-14	47	Medium	Early	unknown
2026-08-13	47	Medium	Early	up
2026-08-12	47	Medium	Early	up
2026-08-11	47	Medium	Early	up
2026-08-10	47	Medium	Early	up
2026-08-09	47	Medium	Early	up
2026-08-08	47	Medium	Early	up
2026-08-07	47	Medium	Early	up
2026-08-06	47	Medium	Early	up
2026-08-05	47	Medium	Early	up
2026-08-04	47	Medium	Early	up
2026-08-03	47	Medium	Early	up
2026-08-02	47	Medium	Early	unknown
2026-08-01	47	Medium	Early	up
2026-07-31	47	Medium	Early	up
2026-07-30	47	Medium	Early	unknown
2026-07-29	47	Medium	Early	up
2026-07-28	47	Medium	Early	up
2026-07-27	47	Medium	Early	up
2026-07-26	47	Medium	Early	up
2026-07-25	47	Medium	Early	up
2026-07-24	47	Medium	Early	up
2026-07-23	47	Medium	Early	up
2026-07-22	47	Medium	Early	up
2026-07-21	47	Medium	Early	up
2026-07-20	47	Medium	Early	unknown
2026-07-19	46	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
Sep 11, 2026
Auto-enriched: supported integrations, has demo, has pricing
Sep 4, 2026
Sato Score tier: Low → Medium
Score 35 → 42.
Sep 3, 2026
Sato Score tier: Medium → Low
Score 42 → 35.
Aug 29, 2026
Sato Score tier: Low → Medium
Score 35 → 42.
Aug 27, 2026
Sato Score tier: Medium → Low
Score 42 → 35.
Aug 1, 2026
Sato Hub began tracking this listing
Jul 20, 2026
Edited: 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