SSyncDev

Pusaka MCP Server

NFTs on NEAR that each control a native Bitcoin address: buy, lend, borrow, inherit, with caps

Local + remotestreamable-httpstdio

What is the Pusaka MCP Server?

Pusaka is an MCP integration. NFTs on NEAR that each control a native Bitcoin address: buy, lend, borrow, inherit, with caps.

Hosted connection

The registry lists a streamable-http connection at https://pusaka-two.vercel.app/api/mcp.

Packages and local setup

The published npm package is pusaka-mcp, version 1.1.2. Its declared MCP transport is stdio.

The package declares PUSAKA_ACCOUNT_ID: NEAR account the agent acts as (optional: read-only without it); PUSAKA_PRIVATE_KEY: Its ed25519 key; PUSAKA_MAX_SPEND_NEAR: Spend cap per session in NEAR (default 5); PUSAKA_CONTRACT: Pusaka contract (default pusaka-v2.testnet; pusaka-btc.testnet for the classic one); PUSAKA_ALLOW_OUTFLOWS: Set to 1 to let the agent move a Pusaka or its assets out; PUSAKA_ALLOWED_RECIPIENTS: Comma-separated accounts or addresses outflows may go to; PUSAKA_CONFIRM: off: no human confirmation even when the host supports elicitation (caps still apply).

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
PUSAKA_ACCOUNT_IDNEAR account the agent acts as (optional: read-only without it)Check documentation
PUSAKA_PRIVATE_KEYIts ed25519 keyCheck documentation
PUSAKA_MAX_SPEND_NEARSpend cap per session in NEAR (default 5)Check documentation
PUSAKA_CONTRACTPusaka contract (default pusaka-v2.testnet; pusaka-btc.testnet for the classic one)Check documentation
PUSAKA_ALLOW_OUTFLOWSSet to 1 to let the agent move a Pusaka or its assets outCheck documentation
PUSAKA_ALLOWED_RECIPIENTSComma-separated accounts or addresses outflows may go toCheck documentation
PUSAKA_CONFIRMoff: no human confirmation even when the host supports elicitation (caps still apply)Check documentation