Sato Hub
← Vybe Solana MCP verification record

Score history

Vybe Solana 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

83

Change over 63d

+23

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-08-255183+32the project
2026-08-106351-12the project
2026-07-155963+4Sato Hub changed the scoring method
2026-07-146059-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 & liveness35/35
35
Code transparency19/20
20
Interface verifiability10/10
10
Docs & demo6/10
10
Listing transparency & provenance13/15
15
Independent verification0/10
10

The observed record

40.3% 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: failed, unattributable2026-07-20: failed, unattributable2026-07-21: failed, unattributable2026-07-22: failed, unattributable2026-07-23: failed, unattributable2026-07-24: failed, unattributable2026-07-25: failed, unattributable2026-07-26: failed, unattributable2026-07-27: failed, unattributable2026-07-28: failed, unattributable2026-07-29: failed, unattributable2026-07-30: failed, unattributable2026-07-31: failed, unattributable2026-08-01: failed, unattributable2026-08-02: failed, unattributable2026-08-03: failed, unattributable2026-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: 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-1383HighActiveup
2026-09-1283HighActiveup
2026-09-1183HighActiveup
2026-09-1083HighActiveup
2026-09-0983HighActiveup
2026-09-0883HighActiveup
2026-09-0783HighActiveup
2026-09-0683HighActiveup
2026-09-0583HighActiveup
2026-09-0483HighActiveup
2026-09-0383HighActiveup
2026-09-0283HighActiveup
2026-09-0183HighActiveup
2026-08-3183HighActiveup
2026-08-3083HighActiveup
2026-08-2983HighActiveup
2026-08-2883HighActiveup
2026-08-2783HighActiveup
2026-08-2683HighActiveup
2026-08-2583HighActiveup
2026-08-2451MediumActiveunknown
2026-08-2351MediumActiveunknown
2026-08-2251MediumActiveunknown
2026-08-2151MediumActiveunknown
2026-08-2051MediumActiveunknown
2026-08-1951MediumActiveunknown
2026-08-1851MediumActiveunknown
2026-08-1751MediumActiveunknown
2026-08-1651MediumActiveunknown
2026-08-1551MediumActiveunknown
2026-08-1451MediumActiveunknown
2026-08-1351MediumActiveunknown
2026-08-1251MediumActiveunknown
2026-08-1151MediumActiveunknown
2026-08-1051MediumActiveunknown
2026-08-0963MediumActiveunknown
2026-08-0863MediumActiveunknown
2026-08-0763MediumActiveunknown
2026-08-0663MediumActiveunknown
2026-08-0563MediumActiveunknown
2026-08-0463MediumActiveunknown
2026-08-0363MediumActiveunknown
2026-08-0263MediumActiveunknown
2026-08-0163MediumActiveunknown
2026-07-3163MediumActiveunknown
2026-07-3063MediumActiveunknown
2026-07-2963MediumActiveunknown
2026-07-2863MediumActiveunknown
2026-07-2763MediumActiveunknown
2026-07-2663MediumActiveunknown
2026-07-2563MediumActiveunknown
2026-07-2463MediumActiveunknown
2026-07-2363MediumActiveunknown
2026-07-2263MediumActiveunknown
2026-07-2163MediumActiveunknown
2026-07-2063MediumActiveunknown
2026-07-1963MediumActiveunknown
2026-07-1863MediumActiveup
2026-07-1763MediumActiveup
2026-07-1663MediumActiveup
2026-07-1563MediumActiveup
2026-07-1459MediumActiveup
2026-07-1360MediumActivenot 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 25, 2026
    Sato Score tier: Medium → High
    Score 51 → 83.
  2. Jul 20, 2026
    Edited: mcp endpoint url
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 14, 2026
    Enriched: has pricing
  5. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  6. Jul 13, 2026
    Listed on Sato Hub
  7. 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.
← Verification recordThis week’s moversDispute this score