Sato Hub
← Polkadot MCP verification record

Score history

Polkadot MCP

Every Sato Hub Sato Score reading we have captured for this listing, one per day, each dated. Days we changed the scoring method are marked separately from days the project moved. How open, active and verifiable — not a safety, quality, or returns grade.

Score today

32

Change over 62d

-14

Days measured

62

Days missed

0

Sato Score, daily

2026-07-14 → 2026-09-13
02550751002026-07-20: Sato Hub changed the scoring method (46 → 47). Not a change by the project.2026-07-14: 46 (Medium)2026-07-15: 46 (Medium)2026-07-16: 46 (Medium)2026-07-17: 46 (Medium)2026-07-18: 46 (Medium)2026-07-19: 46 (Medium)2026-07-20: 47 (Medium)2026-07-21: 47 (Medium)2026-07-22: 47 (Medium)2026-07-23: 47 (Medium)2026-07-24: 47 (Medium)2026-07-25: 47 (Medium)2026-07-26: 47 (Medium)2026-07-27: 47 (Medium)2026-07-28: 47 (Medium)2026-07-29: 47 (Medium)2026-07-30: 47 (Medium)2026-07-31: 47 (Medium)2026-08-01: 47 (Medium)2026-08-02: 47 (Medium)2026-08-03: 47 (Medium)2026-08-04: 40 (Medium)2026-08-05: 40 (Medium)2026-08-06: 40 (Medium)2026-08-07: 40 (Medium)2026-08-08: 40 (Medium)2026-08-09: 40 (Medium)2026-08-10: 40 (Medium)2026-08-11: 40 (Medium)2026-08-12: 40 (Medium)2026-08-13: 40 (Medium)2026-08-14: 40 (Medium)2026-08-15: 40 (Medium)2026-08-16: 40 (Medium)2026-08-17: 40 (Medium)2026-08-18: 40 (Medium)2026-08-19: 40 (Medium)2026-08-20: 40 (Medium)2026-08-21: 40 (Medium)2026-08-22: 40 (Medium)2026-08-23: 40 (Medium)2026-08-24: 40 (Medium)2026-08-25: 40 (Medium)2026-08-26: 40 (Medium)2026-08-27: 40 (Medium)2026-08-28: 40 (Medium)2026-08-29: 40 (Medium)2026-08-30: 40 (Medium)2026-08-31: 40 (Medium)2026-09-01: 40 (Medium)2026-09-02: 40 (Medium)2026-09-03: 40 (Medium)2026-09-04: 40 (Medium)2026-09-05: 40 (Medium)2026-09-06: 40 (Medium)2026-09-07: 40 (Medium)2026-09-08: 32 (Low)2026-09-09: 32 (Low)2026-09-10: 32 (Low)2026-09-11: 32 (Low)2026-09-12: 32 (Low)2026-09-13: 32 (Low)4647322026-07-142026-09-13

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, 1 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-084032-8the project
2026-08-044740-7the project
2026-07-204647+1Sato 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 & liveness5/35
35
Code transparency16/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance11/15
15
Independent verification0/10
10

The observed record

33.9% of Sato Hub's own daily checks succeeded over 62 checks. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side, and before 2026-09-01 no failure recorded why.

2026-07-14: answered our check2026-07-15: answered our check2026-07-16: answered our check2026-07-17: answered our check2026-07-18: answered our check2026-07-19: answered our check2026-07-20: answered our check2026-07-21: answered our check2026-07-22: answered our check2026-07-23: answered our check2026-07-24: answered our check2026-07-25: answered our check2026-07-26: answered our check2026-07-27: answered our check2026-07-28: answered our check2026-07-29: answered our check2026-07-30: answered our check2026-07-31: answered our check2026-08-01: answered our check2026-08-02: answered our check2026-08-03: answered our check2026-08-04: failed, unattributable2026-08-05: failed, unattributable2026-08-06: failed, unattributable2026-08-07: failed, unattributable2026-08-08: failed, unattributable2026-08-09: failed, unattributable2026-08-10: failed, unattributable2026-08-11: failed, unattributable2026-08-12: failed, unattributable2026-08-13: failed, unattributable2026-08-14: failed, unattributable2026-08-15: failed, unattributable2026-08-16: failed, unattributable2026-08-17: failed, unattributable2026-08-18: failed, unattributable2026-08-19: failed, unattributable2026-08-20: failed, unattributable2026-08-21: failed, unattributable2026-08-22: failed, unattributable2026-08-23: failed, unattributable2026-08-24: failed, unattributable2026-08-25: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-09-01: the host answered with an error2026-09-02: the host answered with an error2026-09-03: the host answered with an error2026-09-04: the host answered with an error2026-09-05: the host answered with an error2026-09-06: the host answered with an error2026-09-07: the host answered with an error2026-09-08: the host answered with an error2026-09-09: the host answered with an error2026-09-10: the host answered with an error2026-09-11: the host answered with an error2026-09-12: the host answered with an error2026-09-13: the host answered with an error
  • 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.

DateScoreTierStatusOur check
2026-09-1332LowUnknowndown
2026-09-1232LowUnknowndown
2026-09-1132LowUnknowndown
2026-09-1032LowUnknowndown
2026-09-0932LowUnknowndown
2026-09-0832LowUnknowndown
2026-09-0740MediumUnknowndown
2026-09-0640MediumUnknowndown
2026-09-0540MediumUnknowndown
2026-09-0440MediumUnknowndown
2026-09-0340MediumUnknowndown
2026-09-0240MediumUnknowndown
2026-09-0140MediumUnknowndown
2026-08-3140MediumUnknownunknown
2026-08-3040MediumUnknownunknown
2026-08-2940MediumUnknownunknown
2026-08-2840MediumUnknownunknown
2026-08-2740MediumUnknownunknown
2026-08-2640MediumUnknownunknown
2026-08-2540MediumUnknownunknown
2026-08-2440MediumUnknownunknown
2026-08-2340MediumUnknownunknown
2026-08-2240MediumUnknownunknown
2026-08-2140MediumUnknownunknown
2026-08-2040MediumUnknownunknown
2026-08-1940MediumUnknownunknown
2026-08-1840MediumUnknownunknown
2026-08-1740MediumUnknownunknown
2026-08-1640MediumUnknownunknown
2026-08-1540MediumUnknownunknown
2026-08-1440MediumUnknownunknown
2026-08-1340MediumUnknownunknown
2026-08-1240MediumUnknownunknown
2026-08-1140MediumUnknownunknown
2026-08-1040MediumUnknownunknown
2026-08-0940MediumUnknownunknown
2026-08-0840MediumUnknownunknown
2026-08-0740MediumUnknownunknown
2026-08-0640MediumUnknownunknown
2026-08-0540MediumUnknownunknown
2026-08-0440MediumUnknownunknown
2026-08-0347MediumUnknownup
2026-08-0247MediumUnknownup
2026-08-0147MediumUnknownup
2026-07-3147MediumUnknownup
2026-07-3047MediumUnknownup
2026-07-2947MediumUnknownup
2026-07-2847MediumUnknownup
2026-07-2747MediumUnknownup
2026-07-2647MediumUnknownup
2026-07-2547MediumUnknownup
2026-07-2447MediumUnknownup
2026-07-2347MediumUnknownup
2026-07-2247MediumUnknownup
2026-07-2147MediumUnknownup
2026-07-2047MediumUnknownup
2026-07-1946MediumUnknownup
2026-07-1846MediumUnknownup
2026-07-1746MediumUnknownup
2026-07-1646MediumUnknownup
2026-07-1546MediumUnknownup
2026-07-1446MediumUnknownup

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.

  1. Sep 8, 2026
    Sato Score tier: Medium → Low
    Score 40 → 32.
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 14, 2026
    Auto-enriched: creator profile url, deployment options, supported integrations
  4. Jul 14, 2026
    Listed on Sato Hub
  5. Jul 14, 2026
    Sato Hub began tracking this listing

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 recordThis week’s moversDispute this score