Sato Hub
← Memecoin Observatory MCP verification record

Score history

Memecoin Observatory 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

52

Change over 63d

+10

Days measured

63

Days missed

0

Sato Score, daily

2026-07-13 → 2026-09-13
02550751002026-07-14: Sato Hub changed the scoring method (42 → 48). Not a change by the project.2026-07-20: Sato Hub changed the scoring method (48 → 49). Not a change by the project.2026-09-01: Sato Hub changed the scoring method (49 → 52). Not a change by the project.2026-07-13: 42 (Medium)2026-07-14: 48 (Medium)2026-07-15: 48 (Medium)2026-07-16: 48 (Medium)2026-07-17: 48 (Medium)2026-07-18: 48 (Medium)2026-07-19: 48 (Medium)2026-07-20: 49 (Medium)2026-07-21: 49 (Medium)2026-07-22: 49 (Medium)2026-07-23: 49 (Medium)2026-07-24: 49 (Medium)2026-07-25: 49 (Medium)2026-07-26: 49 (Medium)2026-07-27: 49 (Medium)2026-07-28: 49 (Medium)2026-07-29: 49 (Medium)2026-07-30: 49 (Medium)2026-07-31: 49 (Medium)2026-08-01: 49 (Medium)2026-08-02: 49 (Medium)2026-08-03: 49 (Medium)2026-08-04: 49 (Medium)2026-08-05: 49 (Medium)2026-08-06: 49 (Medium)2026-08-07: 49 (Medium)2026-08-08: 49 (Medium)2026-08-09: 49 (Medium)2026-08-10: 49 (Medium)2026-08-11: 49 (Medium)2026-08-12: 49 (Medium)2026-08-13: 49 (Medium)2026-08-14: 49 (Medium)2026-08-15: 49 (Medium)2026-08-16: 49 (Medium)2026-08-17: 49 (Medium)2026-08-18: 49 (Medium)2026-08-19: 49 (Medium)2026-08-20: 49 (Medium)2026-08-21: 49 (Medium)2026-08-22: 49 (Medium)2026-08-23: 49 (Medium)2026-08-24: 49 (Medium)2026-08-25: 49 (Medium)2026-08-26: 49 (Medium)2026-08-27: 49 (Medium)2026-08-28: 49 (Medium)2026-08-29: 49 (Medium)2026-08-30: 49 (Medium)2026-08-31: 49 (Medium)2026-09-01: 52 (Medium)2026-09-02: 52 (Medium)2026-09-03: 52 (Medium)2026-09-04: 52 (Medium)2026-09-05: 52 (Medium)2026-09-06: 52 (Medium)2026-09-07: 52 (Medium)2026-09-08: 52 (Medium)2026-09-09: 52 (Medium)2026-09-10: 52 (Medium)2026-09-11: 52 (Medium)2026-09-12: 52 (Medium)2026-09-13: 52 (Medium)4252522026-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-014952+3Sato Hub changed the scoring method
2026-07-204849+1Sato Hub changed the scoring method
2026-07-144248+6Sato 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 transparency18/20
20
Interface verifiability0/10
10
Docs & demo0/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-1352MediumUnknownup
2026-09-1252MediumUnknownup
2026-09-1152MediumUnknownup
2026-09-1052MediumUnknownup
2026-09-0952MediumUnknownup
2026-09-0852MediumUnknownup
2026-09-0752MediumUnknownup
2026-09-0652MediumUnknownup
2026-09-0552MediumUnknownup
2026-09-0452MediumUnknownup
2026-09-0352MediumUnknownup
2026-09-0252MediumUnknownup
2026-09-0152MediumUnknownup
2026-08-3149MediumUnknownup
2026-08-3049MediumUnknownup
2026-08-2949MediumUnknownup
2026-08-2849MediumUnknownup
2026-08-2749MediumUnknownup
2026-08-2649MediumUnknownup
2026-08-2549MediumUnknownup
2026-08-2449MediumUnknownup
2026-08-2349MediumUnknownup
2026-08-2249MediumUnknownup
2026-08-2149MediumUnknownup
2026-08-2049MediumUnknownup
2026-08-1949MediumUnknownup
2026-08-1849MediumUnknownup
2026-08-1749MediumUnknownup
2026-08-1649MediumUnknownup
2026-08-1549MediumUnknownup
2026-08-1449MediumUnknownup
2026-08-1349MediumUnknownup
2026-08-1249MediumUnknownup
2026-08-1149MediumUnknownup
2026-08-1049MediumUnknownup
2026-08-0949MediumUnknownup
2026-08-0849MediumUnknownup
2026-08-0749MediumUnknownup
2026-08-0649MediumUnknownup
2026-08-0549MediumUnknownup
2026-08-0449MediumUnknownup
2026-08-0349MediumUnknownup
2026-08-0249MediumUnknownup
2026-08-0149MediumUnknownup
2026-07-3149MediumUnknownup
2026-07-3049MediumUnknownup
2026-07-2949MediumUnknownup
2026-07-2849MediumUnknownup
2026-07-2749MediumUnknownup
2026-07-2649MediumUnknownup
2026-07-2549MediumUnknownup
2026-07-2449MediumUnknownup
2026-07-2349MediumUnknownup
2026-07-2249MediumUnknownup
2026-07-2149MediumUnknownup
2026-07-2049MediumUnknownup
2026-07-1948MediumUnknownup
2026-07-1848MediumUnknownup
2026-07-1748MediumUnknownup
2026-07-1648MediumUnknownup
2026-07-1548MediumUnknownup
2026-07-1448MediumUnknownup
2026-07-1342MediumUnknownnot 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 20, 2026
    Edited: deploy spec
  2. Jul 14, 2026
    Enriched: deployment options, supported integrations
  3. Jul 13, 2026
    Listed on Sato Hub
  4. 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