MCP server for SuperScalar — Bitcoin Lightning channel factories that onboard N users in one shared UTXO. No soft fork required.
| Tool | Description |
|---|---|
superscalar_overview |
Protocol overview — what SuperScalar is, how it works, key properties |
superscalar_estimate_savings |
Estimate on-chain UTXO and fee savings vs individual channel opens |
superscalar_architecture |
Deep dive into a specific component (invalidation tree, timeout tree, channels, MuSig2, watchtower, transport) |
superscalar_resources |
Links to source code, website, papers, and related projects |
npm install -g superscalar-mcpAdd to your claude_desktop_config.json:
{
"mcpServers": {
"superscalar": {
"command": "npx",
"args": ["superscalar-mcp"]
}
}
}claude mcp add superscalar -- npx superscalar-mcpOnce connected, you can ask Claude things like:
- "What is SuperScalar and how does it scale Lightning?"
- "Estimate the savings if 50 users share a channel factory instead of opening individual channels"
- "Explain how the invalidation tree works in SuperScalar"
- "What resources exist for learning about channel factories?"
SuperScalar combines Decker-Wattenhofer invalidation trees, timeout-signature trees, and Poon-Dryja channels to create Lightning channel factories that work today — no consensus changes needed.
- Source: https://github.com/8144225309/SuperScalar
- Website: https://SuperScalar.win
- Implementation: C, 400+ tests, MuSig2, Taproot, watchtower support
MIT