Sato Hub
Mina MCP Server verification record

Score history

Mina MCP Server

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

68

Change over 62d

+9

Days measured

62

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-07-206068+8Sato Hub changed the scoring method
2026-07-155960+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 transparency16/20
20
Interface verifiability8/10
10
Docs & demo0/10
10
Listing transparency & provenance9/15
15
Independent verification0/10
10

The observed record

93.5% 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: failed, unattributable2026-07-16: failed, unattributable2026-07-17: failed, unattributable2026-07-18: failed, unattributable2026-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-1368MediumActiveup
2026-09-1268MediumActiveup
2026-09-1168MediumActiveup
2026-09-1068MediumActiveup
2026-09-0968MediumActiveup
2026-09-0868MediumActiveup
2026-09-0768MediumActiveup
2026-09-0668MediumActiveup
2026-09-0568MediumActiveup
2026-09-0468MediumActiveup
2026-09-0368MediumActiveup
2026-09-0268MediumActiveup
2026-09-0168MediumActiveup
2026-08-3168MediumActiveup
2026-08-3068MediumActiveup
2026-08-2968MediumActiveup
2026-08-2868MediumActiveup
2026-08-2768MediumActiveup
2026-08-2668MediumActiveup
2026-08-2568MediumActiveup
2026-08-2468MediumActiveup
2026-08-2368MediumActiveup
2026-08-2268MediumActiveup
2026-08-2168MediumActiveup
2026-08-2068MediumActiveup
2026-08-1968MediumActiveup
2026-08-1868MediumActiveup
2026-08-1768MediumActiveup
2026-08-1668MediumActiveup
2026-08-1568MediumActiveup
2026-08-1468MediumActiveup
2026-08-1368MediumActiveup
2026-08-1268MediumActiveup
2026-08-1168MediumActiveup
2026-08-1068MediumActiveup
2026-08-0968MediumActiveup
2026-08-0868MediumActiveup
2026-08-0768MediumActiveup
2026-08-0668MediumActiveup
2026-08-0568MediumActiveup
2026-08-0468MediumActiveup
2026-08-0368MediumActiveup
2026-08-0268MediumActiveup
2026-08-0168MediumActiveup
2026-07-3168MediumActiveup
2026-07-3068MediumActiveup
2026-07-2968MediumActiveup
2026-07-2868MediumActiveup
2026-07-2768MediumActiveup
2026-07-2668MediumActiveup
2026-07-2568MediumActiveup
2026-07-2468MediumActiveup
2026-07-2368MediumActiveup
2026-07-2268MediumActiveup
2026-07-2168MediumActiveup
2026-07-2068MediumActiveup
2026-07-1960MediumActiveup
2026-07-1860MediumActiveunknown
2026-07-1760MediumActiveunknown
2026-07-1660MediumActiveunknown
2026-07-1560MediumActiveunknown
2026-07-1459MediumActiveup

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 21, 2026
    Verified: deploy spec
  2. Jul 20, 2026
    Edited: mcp endpoint url
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 14, 2026
    Auto-enriched: deployment options
  5. Jul 14, 2026
    Listed on Sato Hub
  6. 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.