pusaka-mcp
v1.1.2
Published
MCP server for Pusaka: NFTs on NEAR that each control a native Bitcoin address (Chain Signatures), with deposits proven by NEAR's Bitcoin light client. Buy, lend, borrow, inherit, with spend caps.
Maintainers
Readme
pusaka-mcp
MCP server for Pusaka: NEP-171 NFTs on NEAR, each controlling a native Bitcoin address through NEAR Chain Signatures. Deposits are proven by NEAR's Bitcoin light client, so an agent can see exactly how much Bitcoin a Pusaka holds before it buys or lends against it.
{ "mcpServers": { "pusaka": { "command": "npx", "args": ["-y", "pusaka-mcp"],
"env": { "PUSAKA_ACCOUNT_ID": "agent.testnet", "PUSAKA_PRIVATE_KEY": "ed25519:…", "PUSAKA_MAX_SPEND_NEAR": "2" } } } }Without a key the read tools work (pusaka_overview, pusaka_inspect, pusaka_loan_offers, …). With one,
every spend is capped by PUSAKA_MAX_SPEND_NEAR (default 5), purchases by a max price, loans by a max LTV; moving a
Pusaka or its assets out needs PUSAKA_ALLOW_OUTFLOWS=1 (ideally with PUSAKA_ALLOWED_RECIPIENTS).
Network: NEAR testnet (contract pusaka-v2.testnet; PUSAKA_CONTRACT=pusaka-btc.testnet for the frozen classic one). Source: https://github.com/PugarHuda/pusaka/tree/main/mcp
