Sato Hub
Score history

VeChain MCP Server

One dated Sato Score reading per day. Days we changed the scoring method are marked. Not a safety or returns grade.

Score today

81

Change over 108d

+12

Days measured

108

Days missed

0

Sato Score, daily

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

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

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

DateFromToChangeCause
2026-10-197181+10the project
2026-10-148171-10the project
2026-09-247181+10the project
2026-09-188171-10the project
2026-09-017881+3Sato Hub changed the scoring method
2026-08-156878+10the project
2026-08-097868-10the project
2026-07-207078+8Sato Hub changed the scoring method
2026-07-156970+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 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 108 daily checks since 2026-07-14 succeeded. This is the share of OUR checks that succeeded. It is not uptime: a failed check can be on our side. When a check before 2026-09-01 failed, the checks before that date are left out of the rate: the probe counted a bot-block as a failure then and recorded no reason for any failure.

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 check2026-09-14: answered our check2026-09-15: answered our check2026-09-16: answered our check2026-09-17: answered our check2026-09-18: answered our check2026-09-19: answered our check2026-09-20: answered our check2026-09-21: answered our check2026-09-22: answered our check2026-09-23: answered our check2026-09-24: answered our check2026-09-25: answered our check2026-09-26: answered our check2026-09-27: answered our check2026-09-28: answered our check2026-09-29: answered our check2026-09-30: answered our check2026-10-01: answered our check2026-10-02: answered our check2026-10-03: answered our check2026-10-04: answered our check2026-10-05: answered our check2026-10-06: answered our check2026-10-07: answered our check2026-10-08: answered our check2026-10-09: answered our check2026-10-10: answered our check2026-10-11: answered our check2026-10-12: answered our check2026-10-13: answered our check2026-10-14: answered our check2026-10-15: answered our check2026-10-16: answered our check2026-10-17: answered our check2026-10-18: answered our check2026-10-19: answered our check2026-10-20: answered our check2026-10-21: answered our check2026-10-22: answered our check2026-10-23: answered our check2026-10-24: answered our check2026-10-25: answered our check2026-10-26: answered our check2026-10-27: answered our check2026-10-28: answered our check2026-10-29: 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-10-2981HighActiveup
2026-10-2881HighActiveup
2026-10-2781HighActiveup
2026-10-2681HighActiveup
2026-10-2581HighActiveup
2026-10-2481HighActiveup
2026-10-2381HighActiveup
2026-10-2281HighActiveup
2026-10-2181HighActiveup
2026-10-2081HighActiveup
2026-10-1981HighActiveup
2026-10-1871HighActiveup
2026-10-1771HighActiveup
2026-10-1671HighActiveup
2026-10-1571HighActiveup
2026-10-1471HighActiveup
2026-10-1381HighActiveup
2026-10-1281HighActiveup
2026-10-1181HighActiveup
2026-10-1081HighActiveup
2026-10-0981HighActiveup
2026-10-0881HighActiveup
2026-10-0781HighActiveup
2026-10-0681HighActiveup
2026-10-0581HighActiveup
2026-10-0481HighActiveup
2026-10-0381HighActiveup
2026-10-0281HighActiveup
2026-10-0181HighActiveup
2026-09-3081HighActiveup
2026-09-2981HighActiveup
2026-09-2881HighActiveup
2026-09-2781HighActiveup
2026-09-2681HighActiveup
2026-09-2581HighActiveup
2026-09-2481HighActiveup
2026-09-2371HighActiveup
2026-09-2271HighActiveup
2026-09-2171HighActiveup
2026-09-2071HighActiveup
2026-09-1971HighActiveup
2026-09-1871HighActiveup
2026-09-1781HighActiveup
2026-09-1681HighActiveup
2026-09-1581HighActiveup
2026-09-1481HighActiveup
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-0381HighActiveup
2026-09-0281HighActiveup
2026-09-0181HighActiveup
2026-08-3178HighActiveup
2026-08-3078HighActiveup
2026-08-2978HighActiveup
2026-08-2878HighActiveup
2026-08-2778HighActiveup
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-1468MediumActiveup
2026-08-1368MediumActiveup
2026-08-1268MediumActiveup
2026-08-1168MediumActiveup
2026-08-1068MediumActiveup
2026-08-0968MediumActiveup
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-2778HighActiveup
2026-07-2678HighActiveup
2026-07-2578HighActiveup
2026-07-2478HighActiveup
2026-07-2378HighActiveup
2026-07-2278HighActiveup
2026-07-2178HighActiveup
2026-07-2078HighActiveup
2026-07-1970HighActiveup
2026-07-1870HighActiveup
2026-07-1770HighActiveup
2026-07-1670HighActiveup
2026-07-1570HighActiveup
2026-07-1469MediumActiveup

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 19, 2026
    New release published
  2. Aug 15, 2026
    Sato Score tier: Medium → High
    Score 68 → 78.
  3. Aug 9, 2026
    Sato Score tier: High → Medium
    Score 78 → 68.
  4. Aug 1, 2026
    Sato Hub began tracking this listing
  5. Jul 21, 2026
    Verified: deploy spec
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 14, 2026
    Listed on Sato Hub

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.