Sato Hub
Score history

Robinhood Trading MCP

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

Score today

22

Change over 47d

0

Days measured

47

Days missed

0

Sato Score, daily

2026-09-13 → 2026-10-29
02550751002026-09-13: 22 (Low)2026-09-14: 22 (Low)2026-09-15: 22 (Low)2026-09-16: 22 (Low)2026-09-17: 22 (Low)2026-09-18: 22 (Low)2026-09-19: 22 (Low)2026-09-20: 22 (Low)2026-09-21: 22 (Low)2026-09-22: 22 (Low)2026-09-23: 22 (Low)2026-09-24: 22 (Low)2026-09-25: 22 (Low)2026-09-26: 22 (Low)2026-09-27: 22 (Low)2026-09-28: 22 (Low)2026-09-29: 22 (Low)2026-09-30: 22 (Low)2026-10-01: 22 (Low)2026-10-02: 22 (Low)2026-10-03: 22 (Low)2026-10-04: 22 (Low)2026-10-05: 22 (Low)2026-10-06: 22 (Low)2026-10-07: 22 (Low)2026-10-08: 22 (Low)2026-10-09: 22 (Low)2026-10-10: 22 (Low)2026-10-11: 22 (Low)2026-10-12: 22 (Low)2026-10-13: 22 (Low)2026-10-14: 22 (Low)2026-10-15: 22 (Low)2026-10-16: 22 (Low)2026-10-17: 22 (Low)2026-10-18: 22 (Low)2026-10-19: 22 (Low)2026-10-20: 22 (Low)2026-10-21: 22 (Low)2026-10-22: 22 (Low)2026-10-23: 22 (Low)2026-10-24: 22 (Low)2026-10-25: 22 (Low)2026-10-26: 22 (Low)2026-10-27: 22 (Low)2026-10-28: 22 (Low)2026-10-29: 22 (Low)22222026-09-132026-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.

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 & liveness8/35
35
Code transparency0/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance8/15
15
Independent verification0/10
10

The observed record

0% of 47 daily checks since 2026-09-13 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-09-13: the host answered with an error2026-09-14: the host answered with an error2026-09-15: the host answered with an error2026-09-16: the host answered with an error2026-09-17: the host answered with an error2026-09-18: the host answered with an error2026-09-19: the host answered with an error2026-09-20: the host answered with an error2026-09-21: the host answered with an error2026-09-22: the host answered with an error2026-09-23: failed on our side — not attributable to the project2026-09-24: failed on our side — not attributable to the project2026-09-25: failed on our side — not attributable to the project2026-09-26: failed on our side — not attributable to the project2026-09-27: failed on our side — not attributable to the project2026-09-28: failed on our side — not attributable to the project2026-09-29: failed on our side — not attributable to the project2026-09-30: failed on our side — not attributable to the project2026-10-01: failed on our side — not attributable to the project2026-10-02: failed on our side — not attributable to the project2026-10-03: failed on our side — not attributable to the project2026-10-04: failed on our side — not attributable to the project2026-10-05: failed on our side — not attributable to the project2026-10-06: failed on our side — not attributable to the project2026-10-07: failed on our side — not attributable to the project2026-10-08: failed on our side — not attributable to the project2026-10-09: failed on our side — not attributable to the project2026-10-10: failed on our side — not attributable to the project2026-10-11: failed on our side — not attributable to the project2026-10-12: failed on our side — not attributable to the project2026-10-13: failed on our side — not attributable to the project2026-10-14: failed on our side — not attributable to the project2026-10-15: failed on our side — not attributable to the project2026-10-16: failed on our side — not attributable to the project2026-10-17: failed on our side — not attributable to the project2026-10-18: failed on our side — not attributable to the project2026-10-19: failed on our side — not attributable to the project2026-10-20: failed on our side — not attributable to the project2026-10-21: failed on our side — not attributable to the project2026-10-22: failed on our side — not attributable to the project2026-10-23: failed on our side — not attributable to the project2026-10-24: failed on our side — not attributable to the project2026-10-25: failed on our side — not attributable to the project2026-10-26: failed on our side — not attributable to the project2026-10-27: failed on our side — not attributable to the project2026-10-28: failed on our side — not attributable to the project2026-10-29: failed on our side — not attributable to the project
  • 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-2922LowBetainconclusive
2026-10-2822LowBetainconclusive
2026-10-2722LowBetainconclusive
2026-10-2622LowBetainconclusive
2026-10-2522LowBetainconclusive
2026-10-2422LowBetainconclusive
2026-10-2322LowBetainconclusive
2026-10-2222LowBetainconclusive
2026-10-2122LowBetainconclusive
2026-10-2022LowBetainconclusive
2026-10-1922LowBetainconclusive
2026-10-1822LowBetainconclusive
2026-10-1722LowBetainconclusive
2026-10-1622LowBetainconclusive
2026-10-1522LowBetainconclusive
2026-10-1422LowBetainconclusive
2026-10-1322LowBetainconclusive
2026-10-1222LowBetainconclusive
2026-10-1122LowBetainconclusive
2026-10-1022LowBetainconclusive
2026-10-0922LowBetainconclusive
2026-10-0822LowBetainconclusive
2026-10-0722LowBetainconclusive
2026-10-0622LowBetainconclusive
2026-10-0522LowBetainconclusive
2026-10-0422LowBetainconclusive
2026-10-0322LowBetainconclusive
2026-10-0222LowBetainconclusive
2026-10-0122LowBetainconclusive
2026-09-3022LowBetainconclusive
2026-09-2922LowBetainconclusive
2026-09-2822LowBetainconclusive
2026-09-2722LowBetainconclusive
2026-09-2622LowBetainconclusive
2026-09-2522LowBetainconclusive
2026-09-2422LowBetainconclusive
2026-09-2322LowBetainconclusive
2026-09-2222LowBetadown
2026-09-2122LowBetadown
2026-09-2022LowBetadown
2026-09-1922LowBetadown
2026-09-1822LowBetadown
2026-09-1722LowBetadown
2026-09-1622LowBetadown
2026-09-1522LowBetadown
2026-09-1422LowBetadown
2026-09-1322LowBetadown

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 23, 2026
    Edited: website url, description short, description long, tags
  2. Sep 13, 2026
    Sato Hub began tracking this listing
  3. Sep 12, 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.
← Verification recordThis week’s moversDispute this score