Sato Hub
← Insumer MCP Server verification record

Score history

Insumer 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

81

Change over 62d

+23

Days measured

62

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-047181+10the project
2026-09-016871+3Sato Hub changed the scoring method
2026-08-277868-10the project
2026-07-286778+11the project
2026-07-205867+9Sato 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 transparency17/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance12/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-1381HighActiveup
2026-09-1281HighActiveup
2026-09-1181HighActiveup
2026-09-1081HighActiveup
2026-09-0981HighActiveup
2026-09-0881HighActiveup
2026-09-0781HighActiveup
2026-09-0681HighActiveup
2026-09-0581HighActiveup
2026-09-0481HighActiveup
2026-09-0371HighActiveup
2026-09-0271HighActiveup
2026-09-0171HighActiveup
2026-08-3168MediumActiveup
2026-08-3068MediumActiveup
2026-08-2968MediumActiveup
2026-08-2868MediumActiveup
2026-08-2768MediumActiveup
2026-08-2678HighActiveup
2026-08-2578HighActiveup
2026-08-2478HighActiveup
2026-08-2378HighActiveup
2026-08-2278HighActiveup
2026-08-2178HighActiveup
2026-08-2078HighActiveup
2026-08-1978HighActiveup
2026-08-1878HighActiveup
2026-08-1778HighActiveup
2026-08-1678HighActiveup
2026-08-1578HighActiveup
2026-08-1478HighActiveup
2026-08-1378HighActiveup
2026-08-1278HighActiveup
2026-08-1178HighActiveup
2026-08-1078HighActiveup
2026-08-0978HighActiveup
2026-08-0878HighActiveup
2026-08-0778HighActiveup
2026-08-0678HighActiveup
2026-08-0578HighActiveup
2026-08-0478HighActiveup
2026-08-0378HighActiveup
2026-08-0278HighActiveup
2026-08-0178HighActiveup
2026-07-3178HighActiveup
2026-07-3078HighActiveup
2026-07-2978HighActiveup
2026-07-2878HighActiveup
2026-07-2767MediumActiveup
2026-07-2667MediumActiveup
2026-07-2567MediumActiveup
2026-07-2467MediumActiveup
2026-07-2367MediumActiveup
2026-07-2267MediumActiveup
2026-07-2167MediumActiveup
2026-07-2067MediumActiveup
2026-07-1958MediumActiveup
2026-07-1858MediumActiveup
2026-07-1758MediumActiveup
2026-07-1658MediumActiveup
2026-07-1558MediumActiveup
2026-07-1458MediumActiveup

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. Sep 1, 2026
    Sato Score tier: Medium → High
    Score 68 → 71.
  2. Aug 27, 2026
    Sato Score tier: High → Medium
    Score 78 → 68.
  3. Jul 28, 2026
    Sato Score tier: Medium → High
    Score 67 → 78.
  4. Jul 21, 2026
    Verified: deploy spec
  5. Jul 14, 2026
    Enriched: creator profile url
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 14, 2026
    Listed on Sato Hub
  8. 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.
← Verification recordThis week’s moversDispute this score