Sato Hub
← BICScan MCP verification record

Score history

BICScan 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

61

Change over 62d

+5

Days measured

62

Days missed

0

Sato Score, daily

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

1 change attributable to the project, 2 caused by a revision of the scoring method.

DateFromToChangeCause
2026-09-015861+3Sato Hub changed the scoring method
2026-08-285758+1the project
2026-07-155657+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 & liveness20/35
35
Code transparency18/20
20
Interface verifiability0/10
10
Docs & demo6/10
10
Listing transparency & provenance14/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-1361MediumUnknownup
2026-09-1261MediumUnknownup
2026-09-1161MediumUnknownup
2026-09-1061MediumUnknownup
2026-09-0961MediumUnknownup
2026-09-0861MediumUnknownup
2026-09-0761MediumUnknownup
2026-09-0661MediumUnknownup
2026-09-0561MediumUnknownup
2026-09-0461MediumUnknownup
2026-09-0361MediumUnknownup
2026-09-0261MediumUnknownup
2026-09-0161MediumUnknownup
2026-08-3158MediumUnknownup
2026-08-3058MediumUnknownup
2026-08-2958MediumUnknownup
2026-08-2858MediumUnknownup
2026-08-2757MediumUnknownup
2026-08-2657MediumUnknownup
2026-08-2557MediumUnknownup
2026-08-2457MediumUnknownup
2026-08-2357MediumUnknownup
2026-08-2257MediumUnknownup
2026-08-2157MediumUnknownup
2026-08-2057MediumUnknownup
2026-08-1957MediumUnknownup
2026-08-1857MediumUnknownup
2026-08-1757MediumUnknownup
2026-08-1657MediumUnknownup
2026-08-1557MediumUnknownup
2026-08-1457MediumUnknownup
2026-08-1357MediumUnknownup
2026-08-1257MediumUnknownup
2026-08-1157MediumUnknownup
2026-08-1057MediumUnknownup
2026-08-0957MediumUnknownup
2026-08-0857MediumUnknownup
2026-08-0757MediumUnknownup
2026-08-0657MediumUnknownup
2026-08-0557MediumUnknownup
2026-08-0457MediumUnknownup
2026-08-0357MediumUnknownup
2026-08-0257MediumUnknownup
2026-08-0157MediumUnknownup
2026-07-3157MediumUnknownup
2026-07-3057MediumUnknownup
2026-07-2957MediumUnknownup
2026-07-2857MediumUnknownup
2026-07-2757MediumUnknownup
2026-07-2657MediumUnknownup
2026-07-2557MediumUnknownup
2026-07-2457MediumUnknownup
2026-07-2357MediumUnknownup
2026-07-2257MediumUnknownup
2026-07-2157MediumUnknownup
2026-07-2057MediumUnknownup
2026-07-1957MediumUnknownup
2026-07-1857MediumUnknownup
2026-07-1757MediumUnknownup
2026-07-1657MediumUnknownup
2026-07-1557MediumUnknownup
2026-07-1456MediumUnknownup

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 14, 2026
    Enriched: pricing url
  2. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations, has pricing
  3. Jul 14, 2026
    Listed on Sato Hub
  4. Jul 14, 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