Sato Hub
Bitcoin MCP (Bortlesboat) verification record

Score history

Bitcoin MCP (Bortlesboat)

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

81

Change over 62d

+27

Days measured

62

Days missed

0

Sato Score, daily

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

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

DateFromToChangeCause
2026-09-087181+10the project
2026-09-068171-10the project
2026-09-017881+3Sato Hub changed the scoring method
2026-08-076378+15the project
2026-07-205463+9Sato 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 & liveness35/35
35
Code transparency17/20
20
Interface verifiability8/10
10
Docs & demo6/10
10
Listing transparency & provenance12/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-1381HighActiveup
2026-09-1281HighActiveup
2026-09-1181HighActiveup
2026-09-1081HighActiveup
2026-09-0981HighActiveup
2026-09-0881HighActiveup
2026-09-0771HighActiveup
2026-09-0671HighActiveup
2026-09-0581HighActiveup
2026-09-0481HighActiveup
2026-09-0381HighActiveup
2026-09-0281HighActiveup
2026-09-0181HighActiveup
2026-08-3178HighActiveup
2026-08-3078HighActiveup
2026-08-2978HighActiveup
2026-08-2878HighActiveup
2026-08-2778HighActiveup
2026-08-2678HighActiveup
2026-08-2578HighActiveup
2026-08-2478HighActiveup
2026-08-2378HighActiveup
2026-08-2278HighActiveup
2026-08-2178HighActiveup
2026-08-2078HighActiveup
2026-08-1978HighActiveup
2026-08-1878HighActiveup
2026-08-1778HighActiveup
2026-08-1678HighActiveup
2026-08-1578HighActiveup
2026-08-1478HighActiveup
2026-08-1378HighActiveup
2026-08-1278HighActiveup
2026-08-1178HighActiveup
2026-08-1078HighActiveup
2026-08-0978HighActiveup
2026-08-0878HighActiveup
2026-08-0778HighActiveup
2026-08-0663MediumActiveup
2026-08-0563MediumActiveup
2026-08-0463MediumActiveup
2026-08-0363MediumActiveup
2026-08-0263MediumActiveup
2026-08-0163MediumActiveup
2026-07-3163MediumActiveup
2026-07-3063MediumActiveup
2026-07-2963MediumActiveup
2026-07-2863MediumActiveup
2026-07-2763MediumActiveup
2026-07-2663MediumActiveup
2026-07-2563MediumActiveup
2026-07-2463MediumActiveup
2026-07-2363MediumActiveup
2026-07-2263MediumActiveup
2026-07-2163MediumActiveup
2026-07-2063MediumActiveup
2026-07-1954MediumActiveup
2026-07-1854MediumActiveup
2026-07-1754MediumActiveup
2026-07-1654MediumActiveup
2026-07-1554MediumActiveup
2026-07-1454MediumActiveup

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 7, 2026
    New release published
  2. Aug 7, 2026
    Sato Score tier: Medium → High
    Score 63 → 78.
  3. Aug 7, 2026
    Active again — shipped after a quiet spell
  4. Aug 6, 2026
    New release published
  5. Jul 21, 2026
    Verified: deploy spec
  6. Jul 14, 2026
    Auto-enriched: creator profile url, deployment options, supported integrations
  7. Jul 14, 2026
    Listed on Sato Hub
  8. 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.