Sato Hub
Score history

SellTape MCP

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

Score today

52

Change over 2d

+3

Days measured

2

Days missed

0

Sato Score, daily

2026-11-16 → 2026-11-17
02550751002026-11-16: 49 (Medium)2026-11-17: 52 (Medium)49522026-11-162026-11-17

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, 0 caused by a revision of the scoring method.

DateFromToChangeCause
2026-11-174952+3the project

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 transparency0/20
20
Interface verifiability10/10
10
Docs & demo0/10
10
Listing transparency & provenance7/15
15
Independent verification0/10
10

The observed record

2 checks recorded, 2 in the rate window — too few to state a rate. 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-11-16: answered our check2026-11-17: 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-11-1752MediumUnknownup
2026-11-1649MediumUnknownup

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. Nov 17, 2026
    Auto-enriched: has pricing, supported integrations
  2. Nov 16, 2026
    Listed on Sato Hub
  3. Nov 16, 2026
    Sato Hub began tracking this listing
  4. Nov 16, 2026
    Updated: description long

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.