Sato Hub
TON AgentKit MCP verification record

Score history

TON AgentKit 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

40

Change over 63d

+18

Days measured

63

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-013740+3Sato Hub changed the scoring method
2026-07-203637+1Sato Hub changed the scoring method
2026-07-142236+14Sato 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 & liveness20/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance11/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-1340MediumActiveup
2026-09-1240MediumActiveup
2026-09-1140MediumActiveup
2026-09-1040MediumActiveup
2026-09-0940MediumActiveup
2026-09-0840MediumActiveup
2026-09-0740MediumActiveup
2026-09-0640MediumActiveup
2026-09-0540MediumActiveup
2026-09-0440MediumActiveup
2026-09-0340MediumActiveup
2026-09-0240MediumActiveup
2026-09-0140MediumActiveup
2026-08-3137LowActiveup
2026-08-3037LowActiveup
2026-08-2937LowActiveup
2026-08-2837LowActiveup
2026-08-2737LowActiveup
2026-08-2637LowActiveup
2026-08-2537LowActiveup
2026-08-2437LowActiveup
2026-08-2337LowActiveup
2026-08-2237LowActiveup
2026-08-2137LowActiveup
2026-08-2037LowActiveup
2026-08-1937LowActiveup
2026-08-1837LowActiveup
2026-08-1737LowActiveup
2026-08-1637LowActiveup
2026-08-1537LowActiveup
2026-08-1437LowActiveup
2026-08-1337LowActiveup
2026-08-1237LowActiveup
2026-08-1137LowActiveup
2026-08-1037LowActiveup
2026-08-0937LowActiveup
2026-08-0837LowActiveup
2026-08-0737LowActiveup
2026-08-0637LowActiveup
2026-08-0537LowActiveup
2026-08-0437LowActiveup
2026-08-0337LowActiveup
2026-08-0237LowActiveup
2026-08-0137LowActiveup
2026-07-3137LowActiveup
2026-07-3037LowActiveup
2026-07-2937LowActiveup
2026-07-2837LowActiveup
2026-07-2737LowActiveup
2026-07-2637LowActiveup
2026-07-2537LowActiveup
2026-07-2437LowActiveup
2026-07-2337LowActiveup
2026-07-2237LowActiveup
2026-07-2137LowActiveup
2026-07-2037LowActiveup
2026-07-1936LowActiveup
2026-07-1836LowActiveup
2026-07-1736LowActiveup
2026-07-1636LowActiveup
2026-07-1536LowActiveup
2026-07-1436LowActiveup
2026-07-1322LowActivenot 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. Sep 1, 2026
    Sato Score tier: Low → Medium
    Score 37 → 40.
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  4. Jul 13, 2026
    Listed on Sato Hub
  5. 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.