Sato Hub
← Binance MCP Server (community) verification record

Score history

Binance MCP Server (community)

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

72

Change over 62d

+12

Days measured

62

Days missed

0

Sato Score, daily

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

1 change attributable to the project, 3 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-016972+3Sato Hub changed the scoring method
2026-08-197969-10the project
2026-07-206179+18Sato Hub changed the scoring method
2026-07-156061+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 & liveness25/35
35
Code transparency18/20
20
Interface verifiability8/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-1372HighActiveup
2026-09-1272HighActiveup
2026-09-1172HighActiveup
2026-09-1072HighActiveup
2026-09-0972HighActiveup
2026-09-0872HighActiveup
2026-09-0772HighActiveup
2026-09-0672HighActiveup
2026-09-0572HighActiveup
2026-09-0472HighActiveup
2026-09-0372HighActiveup
2026-09-0272HighActiveup
2026-09-0172HighActiveup
2026-08-3169MediumActiveup
2026-08-3069MediumActiveup
2026-08-2969MediumActiveup
2026-08-2869MediumActiveup
2026-08-2769MediumActiveup
2026-08-2669MediumActiveup
2026-08-2569MediumActiveup
2026-08-2469MediumActiveup
2026-08-2369MediumActiveup
2026-08-2269MediumActiveup
2026-08-2169MediumActiveup
2026-08-2069MediumActiveup
2026-08-1969MediumActiveup
2026-08-1879HighActiveup
2026-08-1779HighActiveup
2026-08-1679HighActiveup
2026-08-1579HighActiveup
2026-08-1479HighActiveup
2026-08-1379HighActiveup
2026-08-1279HighActiveup
2026-08-1179HighActiveup
2026-08-1079HighActiveup
2026-08-0979HighActiveup
2026-08-0879HighActiveup
2026-08-0779HighActiveup
2026-08-0679HighActiveup
2026-08-0579HighActiveup
2026-08-0479HighActiveup
2026-08-0379HighActiveup
2026-08-0279HighActiveup
2026-08-0179HighActiveup
2026-07-3179HighActiveup
2026-07-3079HighActiveup
2026-07-2979HighActiveup
2026-07-2879HighActiveup
2026-07-2779HighActiveup
2026-07-2679HighActiveup
2026-07-2579HighActiveup
2026-07-2479HighActiveup
2026-07-2379HighActiveup
2026-07-2279HighActiveup
2026-07-2179HighActiveup
2026-07-2079HighActiveup
2026-07-1961MediumActiveup
2026-07-1861MediumActiveup
2026-07-1761MediumActiveup
2026-07-1661MediumActiveup
2026-07-1561MediumActiveup
2026-07-1460MediumActiveup

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 1, 2026
    Sato Score tier: Medium → High
    Score 69 → 72.
  2. Aug 19, 2026
    Sato Score tier: High → Medium
    Score 79 → 69.
  3. Jul 21, 2026
    Verified: deploy spec
  4. Jul 20, 2026
    Sato Score tier: Medium → High
    Score 61 → 79.
  5. Jul 14, 2026
    Auto-enriched: creator profile url, deployment options, supported integrations
  6. Jul 14, 2026
    Listed on Sato Hub
  7. 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