Sato Hub
← MCP Reference Servers verification record

Score history

MCP Reference Servers

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

73

Change over 63d

+7

Days measured

63

Days missed

0

Sato Score, daily

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

DateFromToChangeCause
2026-09-017073+3Sato Hub changed the scoring method
2026-07-206270+8Sato Hub changed the scoring method
2026-07-197262-10the project
2026-07-186272+10the project
2026-07-156162+1Sato Hub changed the scoring method
2026-07-146661-5Sato 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 transparency20/20
20
Interface verifiability8/10
10
Docs & demo0/10
10
Listing transparency & provenance7/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-1373HighActiveup
2026-09-1273HighActiveup
2026-09-1173HighActiveup
2026-09-1073HighActiveup
2026-09-0973HighActiveup
2026-09-0873HighActiveup
2026-09-0773HighActiveup
2026-09-0673HighActiveup
2026-09-0573HighActiveup
2026-09-0473HighActiveup
2026-09-0373HighActiveup
2026-09-0273HighActiveup
2026-09-0173HighActiveup
2026-08-3170HighActiveup
2026-08-3070HighActiveup
2026-08-2970HighActiveup
2026-08-2870HighActiveup
2026-08-2770HighActiveup
2026-08-2670HighActiveup
2026-08-2570HighActiveup
2026-08-2470HighActiveup
2026-08-2370HighActiveup
2026-08-2270HighActiveup
2026-08-2170HighActiveup
2026-08-2070HighActiveup
2026-08-1970HighActiveup
2026-08-1870HighActiveup
2026-08-1770HighActiveup
2026-08-1670HighActiveup
2026-08-1570HighActiveup
2026-08-1470HighActiveup
2026-08-1370HighActiveup
2026-08-1270HighActiveup
2026-08-1170HighActiveup
2026-08-1070HighActiveup
2026-08-0970HighActiveup
2026-08-0870HighActiveup
2026-08-0770HighActiveup
2026-08-0670HighActiveup
2026-08-0570HighActiveup
2026-08-0470HighActiveup
2026-08-0370HighActiveup
2026-08-0270HighActiveup
2026-08-0170HighActiveup
2026-07-3170HighActiveup
2026-07-3070HighActiveup
2026-07-2970HighActiveup
2026-07-2870HighActiveup
2026-07-2770HighActiveup
2026-07-2670HighActiveup
2026-07-2570HighActiveup
2026-07-2470HighActiveup
2026-07-2370HighActiveup
2026-07-2270HighActiveup
2026-07-2170HighActiveup
2026-07-2070HighActiveup
2026-07-1962MediumActiveup
2026-07-1872HighActiveup
2026-07-1762MediumActiveup
2026-07-1662MediumActiveup
2026-07-1562MediumActiveup
2026-07-1461MediumActiveup
2026-07-1366MediumActivenot 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 31, 2026
    New release published
  2. Aug 18, 2026
    New release published
  3. Jul 21, 2026
    Verified: deploy spec
  4. Jul 20, 2026
    Sato Score tier: Medium → High
    Score 62 → 70.
  5. Jul 19, 2026
    Sato Score tier: High → Medium
    Score 72 → 62.
  6. Jul 18, 2026
    Auto-enriched: docs url, deployment options
  7. Jul 18, 2026
    Sato Score tier: Medium → High
    Score 62 → 72.
  8. Jul 13, 2026
    Listed on Sato Hub
  9. 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