pusaka
io.github.PugarHuda/pusakaVersion 1.1.2NFTs on NEAR that each control a native Bitcoin address: buy, lend, borrow, inherit, with caps
Status
Responds172 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:41 UTC
- Latency
- 172 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://pusaka-two.vercel.app/api/mcpResponds172 msNo sign-in
Claude Code
claude mcp add --transport http pusaka https://pusaka-two.vercel.app/api/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: pusaka
Remote MCP server URL: https://pusaka-two.vercel.app/api/mcpCursor
{
"mcpServers": {
"pusaka": {
"url": "https://pusaka-two.vercel.app/api/mcp"
}
}
}VS Code
code --add-mcp '{"name":"pusaka","type":"http","url":"https://pusaka-two.vercel.app/api/mcp"}'Streamable HTTP
npm: pusaka-mcp 1.1.2Package only
npm (npx)
claude mcp add pusaka -- npx -y pusaka-mcp@1.1.2Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
15 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
pusaka_auditIndependent proof-of-reserves audit of one Pusaka, without trusting the contract's own numbers: asks NEAR's MPC signer which Bitcoin key it derives for this contract and token (must equal the token's key), recomputes verified_sats from the proven deposits minus everything ever signed away, and looks every proven deposit up on Bitcoin itself (confirmed, paying this address, the right amount, and whether it is still unspent). Returns a verdict and each check. | No | Yes | Not declared | Yes |
pusaka_contract_trustShould an agent trust the Pusaka contract itself? Reads from NEAR: the deployed code's sha256 and the reproducible-build source it names (NEP-330), every access key on the contract account (none but one-use gift-link keys means nobody can sign as the contract), whether the code is final (upgrades renounced) or, if not, who can change it (a Sputnik DAO council, its members and vote threshold), the timelock, and any upgrade pending with the time it becomes deployable. | No | Yes | Not declared | Yes |
pusaka_credit_recordA borrower's on-chain credit record across every Pusaka: loans taken, repaid, defaulted (the lender took the collateral) and still open, read from the contract's history, not from anything the borrower says. Use it before funding a loan request or making an offer. | No | Yes | Not declared | Yes |
pusaka_dealsScan every Pusaka for sale for Bitcoin cheaper than it really sells for: each listing's price now (Dutch auctions fall over time) against a live, solver-signed NEAR Intents quote for selling the verified BTC inside into USDC. A negative discount means the NFT costs less than its BTC's exit value. Sorted best deal first. | No | Yes | Not declared | Yes |
pusaka_historyProvenance of one Pusaka from the contract's own on-chain record: every mint, listing, sale and price, transfer, inheritance, loan (funded, repaid, defaulted, refinanced, extended) and withdrawal, oldest first, plus the chain of holders and the sale prices it has fetched. | No | Yes | Not declared | Yes |
pusaka_inspectFull due diligence on one Pusaka: verified BTC and its USD value, a live NEAR Intents quote for selling that BTC (exit value), ETH (safe vs at risk), listing premium, loan LTV, APR and how many times the collateral's exit value covers the loan, sign epoch. | No | Yes | Not declared | Yes |
pusaka_lend_poolThe USDC lending pool (Circle testnet USDC): cash, lent, the BTC price it uses (low side for borrowing, high side for liquidation; null = stale, borrowing and liquidation paused) and every open loan with its debt, loan-to-value and whether it can be liquidated now. With `token_id` (and `contract`), only that Pusaka's loan and the most it could borrow. | No | Yes | Not declared | Yes |
pusaka_loan_offersStanding loan offers from lenders: for one Pusaka, or for any Pusaka holding at least N verified sats. The principal is already escrowed in the contract, so the holder can take it instantly with pusaka_accept_loan_offer, also to refinance a funded loan into cheaper or longer terms. | No | Yes | Not declared | Yes |
pusaka_loan_watchWatch every funded Pusaka loan at once: due date, hours left, loan-to-value at live BTC/NEAR prices, and what this agent can do next on each (repay as borrower, claim the collateral as lender once overdue, or a lender's pending extension to accept). Built for an agent that lends or borrows on a schedule. | No | Yes | Not declared | Yes |
pusaka_market_bookThe market contract's book: standing bids priced per verified sat (best first, with what each would pay for a given Pusaka), loan offers with no due date, and open perpetual loans with their live debt and refinancing-auction rate. | No | Yes | Not declared | Yes |
pusaka_overviewList every Pusaka: owner, BTC verified on NEAR, current sale price, and loan status; plus how many standing loan offers are open and how much NEAR they escrow. | No | Yes | Not declared | Yes |
pusaka_portfolioEverything one NEAR account has in Pusaka: the Pusakas it holds and the Bitcoin proven inside them (sats and USD), loans it owes and loans it funded, standing offers it escrowed, and Pusakas that name it as heir. Defaults to this agent's account. | No | Yes | Not declared | Yes |
pusaka_swap_statusWhere a NEAR Intents swap stands (pusaka_swap_to_usdc): PENDING_DEPOSIT, KNOWN_DEPOSIT_TX, PROCESSING, SUCCESS, REFUNDED or FAILED, with its NEAR settlement transactions and, once settled, the recipient's USDC balance. | No | Yes | Not declared | Yes |
pusaka_token_accountPusaka v2: the NFT's own NEAR account (NEP-616, keyless, answers only to the current holder), its named alias, their balances, what's inside (other Pusakas it holds, with their verified sats, and its USDC: a buyer of this NFT gets all of it), whether the post-quantum (ML-DSA-65) lock is on and open, and any agent's on-chain daily budget. | No | Yes | Not declared | Yes |
pusaka_verify_signatureCheck a signature someone says comes from a Pusaka, the way a website or exchange would: a 'Sign in as Pusaka #N' message (EIP-4361; pass signature 0x…, and domain = your site) or a BIP-322 proof of its Bitcoin address (pass witness, base64). Checks the signature, that the address is the Pusaka's own NEAR MPC key, that the holder it names still holds it, and (sign-ins) expiry and site. Returns valid plus each check. | No | Yes | Not declared | Yes |
Details
- Registry status
- Active
- Published
- Nov 14, 2026
- Updated
- Nov 14, 2026
- Website
- Not given
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared