Sato Hub
Hummingbot MCP verification record

Score history

Hummingbot 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

52

Change over 63d

+21

Days measured

63

Days missed

0

Sato Score, daily

2026-07-132026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (31 → 46). Not a change by the project.2026-07-15: Sato Hub changed the scoring method (46 → 49). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (49 → 52). Not a change by the project.2026-07-13: 31 (Low)2026-07-14: 46 (Medium)2026-07-15: 49 (Medium)2026-07-16: 49 (Medium)2026-07-17: 49 (Medium)2026-07-18: 49 (Medium)2026-07-19: 49 (Medium)2026-07-20: 49 (Medium)2026-07-21: 49 (Medium)2026-07-22: 49 (Medium)2026-07-23: 49 (Medium)2026-07-24: 49 (Medium)2026-07-25: 49 (Medium)2026-07-26: 49 (Medium)2026-07-27: 49 (Medium)2026-07-28: 49 (Medium)2026-07-29: 49 (Medium)2026-07-30: 49 (Medium)2026-07-31: 49 (Medium)2026-08-01: 49 (Medium)2026-08-02: 49 (Medium)2026-08-03: 49 (Medium)2026-08-04: 49 (Medium)2026-08-05: 49 (Medium)2026-08-06: 49 (Medium)2026-08-07: 49 (Medium)2026-08-08: 49 (Medium)2026-08-09: 49 (Medium)2026-08-10: 49 (Medium)2026-08-11: 49 (Medium)2026-08-12: 49 (Medium)2026-08-13: 49 (Medium)2026-08-14: 49 (Medium)2026-08-15: 49 (Medium)2026-08-16: 49 (Medium)2026-08-17: 49 (Medium)2026-08-18: 49 (Medium)2026-08-19: 49 (Medium)2026-08-20: 49 (Medium)2026-08-21: 49 (Medium)2026-08-22: 49 (Medium)2026-08-23: 49 (Medium)2026-08-24: 49 (Medium)2026-08-25: 49 (Medium)2026-08-26: 49 (Medium)2026-08-27: 49 (Medium)2026-08-28: 49 (Medium)2026-08-29: 49 (Medium)2026-08-30: 49 (Medium)2026-08-31: 49 (Medium)2026-09-01: 52 (Medium)2026-09-02: 52 (Medium)2026-09-03: 52 (Medium)2026-09-04: 52 (Medium)2026-09-05: 52 (Medium)2026-09-06: 52 (Medium)2026-09-07: 52 (Medium)2026-09-08: 52 (Medium)2026-09-09: 52 (Medium)2026-09-10: 52 (Medium)2026-09-11: 52 (Medium)2026-09-12: 52 (Medium)2026-09-13: 52 (Medium)3152522026-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-014952+3Sato Hub changed the scoring method
2026-07-154649+3Sato Hub changed the scoring method
2026-07-143146+15Sato 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 transparency18/20
20
Interface verifiability0/10
10
Docs & demo0/10
10
Listing transparency & provenance11/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-1352MediumActiveup
2026-09-1252MediumActiveup
2026-09-1152MediumActiveup
2026-09-1052MediumActiveup
2026-09-0952MediumActiveup
2026-09-0852MediumActiveup
2026-09-0752MediumActiveup
2026-09-0652MediumActiveup
2026-09-0552MediumActiveup
2026-09-0452MediumActiveup
2026-09-0352MediumActiveup
2026-09-0252MediumActiveup
2026-09-0152MediumActiveup
2026-08-3149MediumActiveup
2026-08-3049MediumActiveup
2026-08-2949MediumActiveup
2026-08-2849MediumActiveup
2026-08-2749MediumActiveup
2026-08-2649MediumActiveup
2026-08-2549MediumActiveup
2026-08-2449MediumActiveup
2026-08-2349MediumActiveup
2026-08-2249MediumActiveup
2026-08-2149MediumActiveup
2026-08-2049MediumActiveup
2026-08-1949MediumActiveup
2026-08-1849MediumActiveup
2026-08-1749MediumActiveup
2026-08-1649MediumActiveup
2026-08-1549MediumActiveup
2026-08-1449MediumActiveup
2026-08-1349MediumActiveup
2026-08-1249MediumActiveup
2026-08-1149MediumActiveup
2026-08-1049MediumActiveup
2026-08-0949MediumActiveup
2026-08-0849MediumActiveup
2026-08-0749MediumActiveup
2026-08-0649MediumActiveup
2026-08-0549MediumActiveup
2026-08-0449MediumActiveup
2026-08-0349MediumActiveup
2026-08-0249MediumActiveup
2026-08-0149MediumActiveup
2026-07-3149MediumActiveup
2026-07-3049MediumActiveup
2026-07-2949MediumActiveup
2026-07-2849MediumActiveup
2026-07-2749MediumActiveup
2026-07-2649MediumActiveup
2026-07-2549MediumActiveup
2026-07-2449MediumActiveup
2026-07-2349MediumActiveup
2026-07-2249MediumActiveup
2026-07-2149MediumActiveup
2026-07-2049MediumActiveup
2026-07-1949MediumActiveup
2026-07-1849MediumActiveup
2026-07-1749MediumActiveup
2026-07-1649MediumActiveup
2026-07-1549MediumActiveup
2026-07-1446MediumActiveup
2026-07-1331LowActivenot 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 14, 2026
    Sato Score tier: Low → Medium
    Score 31 → 46.
  3. Jul 13, 2026
    Listed on Sato Hub
  4. 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.