Blockscout MCP Server

This score was committed to a single Merkle root along with every other score we published that day. The root is signed, published, and archivable by anyone — so if we changed this number tomorrow and said it had always been this, the commitment would contradict us. It proves what we published, not that the score is right.

Leaf

41935b6d023185dc9fa1dce8dd504228b7dfe31054541bc2c48ca1fcefc1857a

Preimage

satohub-score-leaf/v1|2026-10-14|blockscout-mcp|80|High

Proof

9 siblings

Root

2026132a6ecc6b220b5e2a6ea862dfbd47f4635b846cc8a89a2e94dbec456122

Root signature

Ed25519, kid b04bd38b

On-chain

not attested on-chain — key absent (ATTEST_PRIVATE_KEY is not set)

Verify this yourself

# 1. The proof: record, leaf, leaf_preimage, proof (sibling digests)
curl -s "https://satohub.ai/api/verify/blockscout-mcp/proof?date=2026-10-14"
# 2. The roots file, fetched separately; take the root for 2026-10-14
curl -s https://satohub.ai/.well-known/sato-score-roots.json
# 3. leaf = SHA-256(leaf_preimage). For each sibling s:
#    leaf = SHA-256("satohub-score-node/v1" || min(leaf,s) || max(leaf,s))
#    The result must equal the root from step 2.
# 4. Check that root's signature against https://satohub.ai/.well-known/jwks.json

No command-line tool is published for score proofs yet; the steps above are the whole check. Compare against the published roots file, not against the root in the proof response — checking a proof only against a root served in the same reply proves nothing. Raw proof: /api/verify/blockscout-mcp/proof. Method: the house rules.