Sato Hub
Privy MCP Server verification record

Score history

Privy 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

58

Change over 63d

+8

Days measured

63

Days missed

0

Sato Score, daily

2026-07-132026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (50 → 54). Not a change by the project.2026-07-15: Sato Hub changed the scoring method (54 → 55). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (55 → 58). Not a change by the project.2026-07-13: 50 (Medium)2026-07-14: 54 (Medium)2026-07-15: 55 (Medium)2026-07-16: 55 (Medium)2026-07-17: 55 (Medium)2026-07-18: 55 (Medium)2026-07-19: 55 (Medium)2026-07-20: 55 (Medium)2026-07-21: 55 (Medium)2026-07-22: 55 (Medium)2026-07-23: 55 (Medium)2026-07-24: 55 (Medium)2026-07-25: 55 (Medium)2026-07-26: 55 (Medium)2026-07-27: 55 (Medium)2026-07-28: 55 (Medium)2026-07-29: 55 (Medium)2026-07-30: 55 (Medium)2026-07-31: 55 (Medium)2026-08-01: 55 (Medium)2026-08-02: 55 (Medium)2026-08-03: 55 (Medium)2026-08-04: 55 (Medium)2026-08-05: 55 (Medium)2026-08-06: 55 (Medium)2026-08-07: 55 (Medium)2026-08-08: 55 (Medium)2026-08-09: 55 (Medium)2026-08-10: 55 (Medium)2026-08-11: 55 (Medium)2026-08-12: 55 (Medium)2026-08-13: 55 (Medium)2026-08-14: 55 (Medium)2026-08-15: 55 (Medium)2026-08-16: 55 (Medium)2026-08-17: 55 (Medium)2026-08-18: 55 (Medium)2026-08-19: 55 (Medium)2026-08-20: 55 (Medium)2026-08-21: 55 (Medium)2026-08-22: 55 (Medium)2026-08-23: 55 (Medium)2026-08-24: 55 (Medium)2026-08-25: 55 (Medium)2026-08-26: 55 (Medium)2026-08-27: 55 (Medium)2026-08-28: 55 (Medium)2026-08-29: 55 (Medium)2026-08-30: 55 (Medium)2026-08-31: 55 (Medium)2026-09-01: 58 (Medium)2026-09-02: 58 (Medium)2026-09-03: 58 (Medium)2026-09-04: 58 (Medium)2026-09-05: 58 (Medium)2026-09-06: 58 (Medium)2026-09-07: 58 (Medium)2026-09-08: 58 (Medium)2026-09-09: 58 (Medium)2026-09-10: 58 (Medium)2026-09-11: 58 (Medium)2026-09-12: 58 (Medium)2026-09-13: 58 (Medium)5058582026-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, 3 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-015558+3Sato Hub changed the scoring method
2026-07-155455+1Sato Hub changed the scoring method
2026-07-145054+4Sato 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
35
Code transparency17/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance12/15
15
Independent verification3/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-1358MediumUnknownup
2026-09-1258MediumUnknownup
2026-09-1158MediumUnknownup
2026-09-1058MediumUnknownup
2026-09-0958MediumUnknownup
2026-09-0858MediumUnknownup
2026-09-0758MediumUnknownup
2026-09-0658MediumUnknownup
2026-09-0558MediumUnknownup
2026-09-0458MediumUnknownup
2026-09-0358MediumUnknownup
2026-09-0258MediumUnknownup
2026-09-0158MediumUnknownup
2026-08-3155MediumUnknownup
2026-08-3055MediumUnknownup
2026-08-2955MediumUnknownup
2026-08-2855MediumUnknownup
2026-08-2755MediumUnknownup
2026-08-2655MediumUnknownup
2026-08-2555MediumUnknownup
2026-08-2455MediumUnknownup
2026-08-2355MediumUnknownup
2026-08-2255MediumUnknownup
2026-08-2155MediumUnknownup
2026-08-2055MediumUnknownup
2026-08-1955MediumUnknownup
2026-08-1855MediumUnknownup
2026-08-1755MediumUnknownup
2026-08-1655MediumUnknownup
2026-08-1555MediumUnknownup
2026-08-1455MediumUnknownup
2026-08-1355MediumUnknownup
2026-08-1255MediumUnknownup
2026-08-1155MediumUnknownup
2026-08-1055MediumUnknownup
2026-08-0955MediumUnknownup
2026-08-0855MediumUnknownup
2026-08-0755MediumUnknownup
2026-08-0655MediumUnknownup
2026-08-0555MediumUnknownup
2026-08-0455MediumUnknownup
2026-08-0355MediumUnknownup
2026-08-0255MediumUnknownup
2026-08-0155MediumUnknownup
2026-07-3155MediumUnknownup
2026-07-3055MediumUnknownup
2026-07-2955MediumUnknownup
2026-07-2855MediumUnknownup
2026-07-2755MediumUnknownup
2026-07-2655MediumUnknownup
2026-07-2555MediumUnknownup
2026-07-2455MediumUnknownup
2026-07-2355MediumUnknownup
2026-07-2255MediumUnknownup
2026-07-2155MediumUnknownup
2026-07-2055MediumUnknownup
2026-07-1955MediumUnknownup
2026-07-1855MediumUnknownup
2026-07-1755MediumUnknownup
2026-07-1655MediumUnknownup
2026-07-1555MediumUnknownup
2026-07-1454MediumUnknownup
2026-07-1350MediumUnknownnot 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. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  2. Jul 13, 2026
    Listed on Sato Hub
  3. 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.