Sato Hub
DexPaprika MCP Server verification record

Score history

DexPaprika MCP Server

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

84

Change over 63d

+11

Days measured

63

Days missed

0

Sato Score, daily

2026-07-132026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (73 → 78). Not a change by the project.2026-07-15: Sato Hub changed the scoring method (78 → 79). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (79 → 81). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (81 → 84). Not a change by the project.2026-07-13: 73 (High)2026-07-14: 78 (High)2026-07-15: 79 (High)2026-07-16: 79 (High)2026-07-17: 79 (High)2026-07-18: 79 (High)2026-07-19: 79 (High)2026-07-20: 81 (High)2026-07-21: 81 (High)2026-07-22: 81 (High)2026-07-23: 81 (High)2026-07-24: 81 (High)2026-07-25: 81 (High)2026-07-26: 81 (High)2026-07-27: 81 (High)2026-07-28: 81 (High)2026-07-29: 81 (High)2026-07-30: 81 (High)2026-07-31: 81 (High)2026-08-01: 81 (High)2026-08-02: 81 (High)2026-08-03: 81 (High)2026-08-04: 81 (High)2026-08-05: 81 (High)2026-08-06: 81 (High)2026-08-07: 81 (High)2026-08-08: 81 (High)2026-08-09: 81 (High)2026-08-10: 81 (High)2026-08-11: 81 (High)2026-08-12: 81 (High)2026-08-13: 81 (High)2026-08-14: 81 (High)2026-08-15: 81 (High)2026-08-16: 81 (High)2026-08-17: 81 (High)2026-08-18: 81 (High)2026-08-19: 81 (High)2026-08-20: 81 (High)2026-08-21: 81 (High)2026-08-22: 81 (High)2026-08-23: 81 (High)2026-08-24: 81 (High)2026-08-25: 81 (High)2026-08-26: 81 (High)2026-08-27: 81 (High)2026-08-28: 81 (High)2026-08-29: 81 (High)2026-08-30: 81 (High)2026-08-31: 81 (High)2026-09-01: 84 (High)2026-09-02: 84 (High)2026-09-03: 84 (High)2026-09-04: 84 (High)2026-09-05: 84 (High)2026-09-06: 84 (High)2026-09-07: 84 (High)2026-09-08: 84 (High)2026-09-09: 84 (High)2026-09-10: 84 (High)2026-09-11: 84 (High)2026-09-12: 84 (High)2026-09-13: 84 (High)7384842026-07-132026-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

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

DateFromToChangeCause
2026-09-018184+3Sato Hub changed the scoring method
2026-07-207981+2Sato Hub changed the scoring method
2026-07-157879+1Sato Hub changed the scoring method
2026-07-147378+5Sato 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
35
Code transparency18/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification5/10
10

The observed record

100% 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: answered our check2026-08-05: answered our check2026-08-06: answered our check2026-08-07: answered our check2026-08-08: answered our check2026-08-09: answered our check2026-08-10: answered our check2026-08-11: answered our check2026-08-12: answered our check2026-08-13: answered our check2026-08-14: answered our check2026-08-15: answered our check2026-08-16: answered our check2026-08-17: answered our check2026-08-18: answered our check2026-08-19: answered our check2026-08-20: answered our check2026-08-21: answered our check2026-08-22: answered our check2026-08-23: answered our check2026-08-24: answered our check2026-08-25: answered our check2026-08-26: answered our check2026-08-27: answered our check2026-08-28: answered our check2026-08-29: answered our check2026-08-30: answered our check2026-08-31: answered our check2026-09-01: answered our check2026-09-02: answered our check2026-09-03: answered our check2026-09-04: answered our check2026-09-05: answered our check2026-09-06: answered our check2026-09-07: answered our check2026-09-08: answered our check2026-09-09: answered our check2026-09-10: answered our check2026-09-11: answered our check2026-09-12: answered our check2026-09-13: answered our check
  • 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-1384HighActiveup
2026-09-1284HighActiveup
2026-09-1184HighActiveup
2026-09-1084HighActiveup
2026-09-0984HighActiveup
2026-09-0884HighActiveup
2026-09-0784HighActiveup
2026-09-0684HighActiveup
2026-09-0584HighActiveup
2026-09-0484HighActiveup
2026-09-0384HighActiveup
2026-09-0284HighActiveup
2026-09-0184HighActiveup
2026-08-3181HighActiveup
2026-08-3081HighActiveup
2026-08-2981HighActiveup
2026-08-2881HighActiveup
2026-08-2781HighActiveup
2026-08-2681HighActiveup
2026-08-2581HighActiveup
2026-08-2481HighActiveup
2026-08-2381HighActiveup
2026-08-2281HighActiveup
2026-08-2181HighActiveup
2026-08-2081HighActiveup
2026-08-1981HighActiveup
2026-08-1881HighActiveup
2026-08-1781HighActiveup
2026-08-1681HighActiveup
2026-08-1581HighActiveup
2026-08-1481HighActiveup
2026-08-1381HighActiveup
2026-08-1281HighActiveup
2026-08-1181HighActiveup
2026-08-1081HighActiveup
2026-08-0981HighActiveup
2026-08-0881HighActiveup
2026-08-0781HighActiveup
2026-08-0681HighActiveup
2026-08-0581HighActiveup
2026-08-0481HighActiveup
2026-08-0381HighActiveup
2026-08-0281HighActiveup
2026-08-0181HighActiveup
2026-07-3181HighActiveup
2026-07-3081HighActiveup
2026-07-2981HighActiveup
2026-07-2881HighActiveup
2026-07-2781HighActiveup
2026-07-2681HighActiveup
2026-07-2581HighActiveup
2026-07-2481HighActiveup
2026-07-2381HighActiveup
2026-07-2281HighActiveup
2026-07-2181HighActiveup
2026-07-2081HighActiveup
2026-07-1979HighActiveup
2026-07-1879HighActiveup
2026-07-1779HighActiveup
2026-07-1679HighActiveup
2026-07-1579HighActiveup
2026-07-1478HighActiveup
2026-07-1373HighActivenot checked

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. Aug 14, 2026
    New release published
  2. Aug 5, 2026
    New release published
  3. Jul 29, 2026
    4 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  4. Jul 20, 2026
    Edited: mcp endpoint url
  5. Jul 19, 2026
    Edited: mcp endpoint url
  6. Jul 14, 2026
    Enriched: supported integrations
  7. Jul 14, 2026
    Auto-enriched: deployment options
  8. Jul 13, 2026
    Listed on Sato Hub
  9. Jul 13, 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.