Sato Hub
Octav API MCP verification record

Score history

Octav API 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

56

Change over 63d

+17

Days measured

63

Days missed

0

Sato Score, daily

2026-07-132026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (39 → 47). Not a change by the project.2026-07-15: Sato Hub changed the scoring method (47 → 63). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (53 → 56). Not a change by the project.2026-07-13: 39 (Low)2026-07-14: 47 (Medium)2026-07-15: 63 (Medium)2026-07-16: 63 (Medium)2026-07-17: 63 (Medium)2026-07-18: 63 (Medium)2026-07-19: 63 (Medium)2026-07-20: 63 (Medium)2026-07-21: 63 (Medium)2026-07-22: 63 (Medium)2026-07-23: 63 (Medium)2026-07-24: 63 (Medium)2026-07-25: 63 (Medium)2026-07-26: 63 (Medium)2026-07-27: 53 (Medium)2026-07-28: 53 (Medium)2026-07-29: 53 (Medium)2026-07-30: 53 (Medium)2026-07-31: 53 (Medium)2026-08-01: 53 (Medium)2026-08-02: 53 (Medium)2026-08-03: 53 (Medium)2026-08-04: 53 (Medium)2026-08-05: 53 (Medium)2026-08-06: 53 (Medium)2026-08-07: 53 (Medium)2026-08-08: 53 (Medium)2026-08-09: 53 (Medium)2026-08-10: 53 (Medium)2026-08-11: 53 (Medium)2026-08-12: 53 (Medium)2026-08-13: 53 (Medium)2026-08-14: 53 (Medium)2026-08-15: 53 (Medium)2026-08-16: 53 (Medium)2026-08-17: 53 (Medium)2026-08-18: 53 (Medium)2026-08-19: 53 (Medium)2026-08-20: 53 (Medium)2026-08-21: 53 (Medium)2026-08-22: 53 (Medium)2026-08-23: 53 (Medium)2026-08-24: 53 (Medium)2026-08-25: 53 (Medium)2026-08-26: 53 (Medium)2026-08-27: 53 (Medium)2026-08-28: 53 (Medium)2026-08-29: 53 (Medium)2026-08-30: 53 (Medium)2026-08-31: 53 (Medium)2026-09-01: 56 (Medium)2026-09-02: 56 (Medium)2026-09-03: 56 (Medium)2026-09-04: 56 (Medium)2026-09-05: 56 (Medium)2026-09-06: 56 (Medium)2026-09-07: 56 (Medium)2026-09-08: 56 (Medium)2026-09-09: 56 (Medium)2026-09-10: 56 (Medium)2026-09-11: 56 (Medium)2026-09-12: 56 (Medium)2026-09-13: 56 (Medium)3963562026-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-09-015356+3Sato Hub changed the scoring method
2026-07-276353-10the project
2026-07-154763+16Sato Hub changed the scoring method
2026-07-143947+8Sato 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 transparency16/20
20
Interface verifiability0/10
10
Docs & demo0/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-1356MediumActiveup
2026-09-1256MediumActiveup
2026-09-1156MediumActiveup
2026-09-1056MediumActiveup
2026-09-0956MediumActiveup
2026-09-0856MediumActiveup
2026-09-0756MediumActiveup
2026-09-0656MediumActiveup
2026-09-0556MediumActiveup
2026-09-0456MediumActiveup
2026-09-0356MediumActiveup
2026-09-0256MediumActiveup
2026-09-0156MediumActiveup
2026-08-3153MediumActiveup
2026-08-3053MediumActiveup
2026-08-2953MediumActiveup
2026-08-2853MediumActiveup
2026-08-2753MediumActiveup
2026-08-2653MediumActiveup
2026-08-2553MediumActiveup
2026-08-2453MediumActiveup
2026-08-2353MediumActiveup
2026-08-2253MediumActiveup
2026-08-2153MediumActiveup
2026-08-2053MediumActiveup
2026-08-1953MediumActiveup
2026-08-1853MediumActiveup
2026-08-1753MediumActiveup
2026-08-1653MediumActiveup
2026-08-1553MediumActiveup
2026-08-1453MediumActiveup
2026-08-1353MediumActiveup
2026-08-1253MediumActiveup
2026-08-1153MediumActiveup
2026-08-1053MediumActiveup
2026-08-0953MediumActiveup
2026-08-0853MediumActiveup
2026-08-0753MediumActiveup
2026-08-0653MediumActiveup
2026-08-0553MediumActiveup
2026-08-0453MediumActiveup
2026-08-0353MediumActiveup
2026-08-0253MediumActiveup
2026-08-0153MediumActiveup
2026-07-3153MediumActiveup
2026-07-3053MediumActiveup
2026-07-2953MediumActiveup
2026-07-2853MediumActiveup
2026-07-2753MediumActiveup
2026-07-2663MediumActiveup
2026-07-2563MediumActiveup
2026-07-2463MediumActiveup
2026-07-2363MediumActiveup
2026-07-2263MediumActiveup
2026-07-2163MediumActiveup
2026-07-2063MediumActiveup
2026-07-1963MediumActiveup
2026-07-1863MediumActiveup
2026-07-1763MediumActiveup
2026-07-1663MediumActiveup
2026-07-1563MediumActiveup
2026-07-1447MediumActiveup
2026-07-1339LowActivenot 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 15, 2026
    Active again — shipped after a quiet spell
  2. Jul 14, 2026
    Enriched: has pricing
  3. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  4. Jul 14, 2026
    Sato Score tier: Low → Medium
    Score 39 → 47.
  5. Jul 13, 2026
    Listed on Sato Hub
  6. 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.