pusaka MCP server
io.github.PugarHuda/pusakaPugarHudastreamable-httpv1.1.2Scanned
NFTs on NEAR that each control a native Bitcoin address: buy, lend, borrow, inherit, with caps
15 tools: 12 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 15
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
12 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the pusaka MCP server can do
The pusaka MCP server is published by the GitHub account PugarHuda. It has 15 tools. It can create or change data (12 tools: pusaka_loan_offers, pusaka_token_account, pusaka_lend_pool, pusaka_market_book and 8 more), but cannot delete data. 3 tools only read.
15 tools bring in text other people can write (pusaka_overview, pusaka_inspect, pusaka_loan_offers and 12 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 14, 2026, version 1.1.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
15 tools
Changes things 12Claude Code: ask
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 (mus…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Independent 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
pusaka_contract_trustShould an agent trust the Pusaka contract itself?Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Should 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it A 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 f…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Scan 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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)…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Provenance 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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) a…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
pusaka_loan_offersStanding loan offers from lenders: for one Pusaka, or for any Pusaka holding at least N verified sats.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Standing 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 collatera…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Watch 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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, a…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Everything 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 ver…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Pusaka 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
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…Reads text others writeNo findings
Why it is in this group
- The name "pusaka_inspect" says "inspect": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Full 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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 …Reads text others writeNo findings
Why it is in this group
- The name "pusaka_swap_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Where 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write15
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:21 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 12
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pusaka-two.vercel.app/api/mcp: tools/list returned 15 tools to an anonymous client, including pusaka_loan_offers (write), pusaka_token_account (write), pusaka_lend_pool (write), pusaka_market_book (write), pusaka_verify_signature (write) and 7 more
Posture changes
- Nov 19, 2026
- Tools that change things, listed without credentials: 10 to 12
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 12.View diff
- Tools that change things, listed without credentials: 10 to 12
Tools1 changed.~1 changedView diff
- Changed:pusaka_lend_poolChanges thingsdescription
Tools2 added.+2 addedView diff
- Added:pusaka_lend_poolChanges things
- Added:pusaka_verify_signatureChanges things
Install
Pinned to version 1.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http pusaka https://pusaka-two.vercel.app/api/mcpclaude mcp add --transport http pusaka https://pusaka-two.vercel.app/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pusaka__pusaka_overview",
"mcp__pusaka__pusaka_inspect",
"mcp__pusaka__pusaka_swap_status"
],
"ask": [
"mcp__pusaka__pusaka_loan_offers",
"mcp__pusaka__pusaka_token_account",
"mcp__pusaka__pusaka_lend_pool",
"mcp__pusaka__pusaka_market_book",
"mcp__pusaka__pusaka_verify_signature",
"mcp__pusaka__pusaka_audit",
"mcp__pusaka__pusaka_contract_trust",
"mcp__pusaka__pusaka_history",
"mcp__pusaka__pusaka_credit_record",
"mcp__pusaka__pusaka_loan_watch",
"mcp__pusaka__pusaka_deals",
"mcp__pusaka__pusaka_portfolio"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pusaka. Review it before you use it.
Capability tags behind 15 rules
- mcp__pusaka__pusaka_overview untrusted-input
- mcp__pusaka__pusaka_inspect untrusted-input
- mcp__pusaka__pusaka_loan_offers untrusted-input
- mcp__pusaka__pusaka_swap_status untrusted-input
- mcp__pusaka__pusaka_token_account untrusted-input
- mcp__pusaka__pusaka_lend_pool untrusted-input
- mcp__pusaka__pusaka_market_book untrusted-input
- mcp__pusaka__pusaka_verify_signature untrusted-input
- mcp__pusaka__pusaka_audit untrusted-input
- mcp__pusaka__pusaka_contract_trust untrusted-input
- mcp__pusaka__pusaka_history untrusted-input
- mcp__pusaka__pusaka_credit_record untrusted-input
- mcp__pusaka__pusaka_loan_watch untrusted-input
- mcp__pusaka__pusaka_deals untrusted-input
- mcp__pusaka__pusaka_portfolio untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.PugarHuda/pusaka/verify?hash=dcc89bb52b71b5b5beff0a5737661f63bbc75ea381dee0feebf445e23acb5982" | jq -e '.changed == false'Pinned hash dcc89bb52b71, from Nov 14, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.PugarHuda/pusaka/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.PugarHuda/pusaka)Source: MCP Registry · repository. Synced Nov 14, 2026, 07:17 UTC.
pusaka MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the pusaka MCP server safe?
- No scan can promise that. What its definitions show: 15 tools, 12 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the pusaka MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the pusaka MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the pusaka MCP server have?
- 15 tools: 12 write, 3 read. pusaka_loan_offers, pusaka_token_account, pusaka_lend_pool, pusaka_market_book, pusaka_verify_signature, pusaka_audit, pusaka_contract_trust, pusaka_history and 7 more.
Does the pusaka MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the pusaka MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the pusaka MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.