Sato Hub
← QuickNode MCP verification record

Score history

QuickNode 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

39

Change over 63d

+17

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-08-223539+4the project
2026-08-143935-4the project
2026-07-203239+7Sato Hub changed the scoring method
2026-07-194432-12the project
2026-07-142244+22Sato 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 & liveness8/35
35
Code transparency0/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance11/15
15
Independent verification6/10
10

The observed record

8.1% 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: failed, unattributable2026-08-26: failed, unattributable2026-08-27: failed, unattributable2026-08-28: failed, unattributable2026-08-29: failed, unattributable2026-08-30: failed, unattributable2026-08-31: failed, unattributable2026-09-01: the host answered with an error2026-09-02: the host answered with an error2026-09-03: the host answered with an error2026-09-04: the host answered with an error2026-09-05: the host answered with an error2026-09-06: the host answered with an error2026-09-07: the host answered with an error2026-09-08: the host answered with an error2026-09-09: the host answered with an error2026-09-10: the host answered with an error2026-09-11: the host answered with an error2026-09-12: the host answered with an error2026-09-13: the host answered with an error
  • 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-1339LowActivedown
2026-09-1239LowActivedown
2026-09-1139LowActivedown
2026-09-1039LowActivedown
2026-09-0939LowActivedown
2026-09-0839LowActivedown
2026-09-0739LowActivedown
2026-09-0639LowActivedown
2026-09-0539LowActivedown
2026-09-0439LowActivedown
2026-09-0339LowActivedown
2026-09-0239LowActivedown
2026-09-0139LowActivedown
2026-08-3139LowActiveunknown
2026-08-3039LowActiveunknown
2026-08-2939LowActiveunknown
2026-08-2839LowActiveunknown
2026-08-2739LowActiveunknown
2026-08-2639LowActiveunknown
2026-08-2539LowActiveunknown
2026-08-2439LowActiveunknown
2026-08-2339LowActiveunknown
2026-08-2239LowActiveunknown
2026-08-2135LowActiveunknown
2026-08-2035LowActiveunknown
2026-08-1935LowActiveunknown
2026-08-1835LowActiveunknown
2026-08-1735LowActiveunknown
2026-08-1635LowActiveunknown
2026-08-1535LowActiveunknown
2026-08-1435LowActiveunknown
2026-08-1339LowActiveunknown
2026-08-1239LowActiveunknown
2026-08-1139LowActiveunknown
2026-08-1039LowActiveunknown
2026-08-0939LowActiveunknown
2026-08-0839LowActiveunknown
2026-08-0739LowActiveunknown
2026-08-0639LowActiveunknown
2026-08-0539LowActiveunknown
2026-08-0439LowActiveunknown
2026-08-0339LowActiveunknown
2026-08-0239LowActiveunknown
2026-08-0139LowActiveunknown
2026-07-3139LowActiveunknown
2026-07-3039LowActiveunknown
2026-07-2939LowActiveunknown
2026-07-2839LowActiveunknown
2026-07-2739LowActiveunknown
2026-07-2639LowActiveunknown
2026-07-2539LowActiveunknown
2026-07-2439LowActiveunknown
2026-07-2339LowActiveunknown
2026-07-2239LowActiveunknown
2026-07-2139LowActiveunknown
2026-07-2039LowActiveunknown
2026-07-1932LowActiveunknown
2026-07-1844MediumActiveup
2026-07-1744MediumActiveup
2026-07-1644MediumActiveup
2026-07-1544MediumActiveup
2026-07-1444MediumActiveup
2026-07-1322LowActivenot 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 20, 2026
    Edited: mcp endpoint url
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 19, 2026
    Sato Score tier: Medium → Low
    Score 44 → 32.
  5. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  6. Jul 14, 2026
    Sato Score tier: Low → Medium
    Score 22 → 44.
  7. Jul 13, 2026
    Listed on Sato Hub
  8. 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