Sato Hub
← Nodit MCP Server verification record

Score history

Nodit 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

69

Change over 63d

-4

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-07-237969-10the project
2026-07-207179+8Sato Hub changed the scoring method
2026-07-157071+1Sato Hub changed the scoring method
2026-07-147370-3Sato 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 verification0/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-1369MediumActivedown
2026-09-1269MediumActivedown
2026-09-1169MediumActivedown
2026-09-1069MediumActivedown
2026-09-0969MediumActivedown
2026-09-0869MediumActivedown
2026-09-0769MediumActivedown
2026-09-0669MediumActivedown
2026-09-0569MediumActivedown
2026-09-0469MediumActivedown
2026-09-0369MediumActivedown
2026-09-0269MediumActivedown
2026-09-0169MediumActivedown
2026-08-3169MediumActiveunknown
2026-08-3069MediumActiveunknown
2026-08-2969MediumActiveunknown
2026-08-2869MediumActiveunknown
2026-08-2769MediumActiveunknown
2026-08-2669MediumActiveunknown
2026-08-2569MediumActiveunknown
2026-08-2469MediumActiveunknown
2026-08-2369MediumActiveunknown
2026-08-2269MediumActiveunknown
2026-08-2169MediumActiveunknown
2026-08-2069MediumActiveunknown
2026-08-1969MediumActiveunknown
2026-08-1869MediumActiveunknown
2026-08-1769MediumActiveunknown
2026-08-1669MediumActiveunknown
2026-08-1569MediumActiveunknown
2026-08-1469MediumActiveunknown
2026-08-1369MediumActiveunknown
2026-08-1269MediumActiveunknown
2026-08-1169MediumActiveunknown
2026-08-1069MediumActiveunknown
2026-08-0969MediumActiveunknown
2026-08-0869MediumActiveunknown
2026-08-0769MediumActiveunknown
2026-08-0669MediumActiveunknown
2026-08-0569MediumActiveunknown
2026-08-0469MediumActiveunknown
2026-08-0369MediumActiveunknown
2026-08-0269MediumActiveunknown
2026-08-0169MediumActiveunknown
2026-07-3169MediumActiveunknown
2026-07-3069MediumActiveunknown
2026-07-2969MediumActiveunknown
2026-07-2869MediumActiveunknown
2026-07-2769MediumActiveunknown
2026-07-2669MediumActiveunknown
2026-07-2569MediumActiveunknown
2026-07-2469MediumActiveunknown
2026-07-2369MediumActiveunknown
2026-07-2279HighActiveunknown
2026-07-2179HighActiveunknown
2026-07-2079HighActiveunknown
2026-07-1971HighActiveunknown
2026-07-1871HighActiveup
2026-07-1771HighActiveup
2026-07-1671HighActiveup
2026-07-1571HighActiveup
2026-07-1470HighActiveup
2026-07-1373HighActivenot 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 23, 2026
    Sato Score tier: High → Medium
    Score 79 → 69.
  2. Jul 21, 2026
    Verified: deploy spec
  3. Jul 20, 2026
    Edited: mcp endpoint url
  4. Jul 19, 2026
    Edited: mcp endpoint url
  5. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  6. Jul 13, 2026
    Listed on Sato Hub
  7. 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