Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Stx402 Agent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
DEPRECATED: This package has moved to @aibtc/mcp-server. Run: npx @aibtc/mcp-server@latest --install
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user stx402-agent-mcp '--' npx -y stx402-agent
# 2 — ask your agent for something these tools do
# pillar_connect, pillar_disconnect, pillar_status and 173 more
Stx402 Agent costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Stx402 Agent as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user stx402-agent-mcp '--' npx -y stx402-agentReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
176 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Connect to your Pillar smart wallet. Opens the Pillar website - if you
No parameter schema on file.
Disconnect from Pillar. Clears locally stored wallet address.
No parameter schema on file.
Check if you
No parameter schema on file.
Send sBTC from your Pillar smart wallet. Requires being connected first (use pillar_connect).
No parameter schema on file.
Fund your Pillar smart wallet. Supports multiple methods:
No parameter schema on file.
Add a backup admin address to your Pillar smart wallet for recovery purposes.
No parameter schema on file.
Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol.
No parameter schema on file.
Configure auto-compound for your Pillar wallet.
No parameter schema on file.
Close or reduce your leveraged sBTC position.
No parameter schema on file.
Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet.
No parameter schema on file.
View your Pillar wallet balance and Zest position.
No parameter schema on file.
Create a new Pillar smart wallet. Opens the Pillar website to complete registration.
No parameter schema on file.
Get your Pillar referral link to invite friends. Share this link and earn rewards when friends sign up.
No parameter schema on file.
Invite a DCA partner by email or wallet address.
No parameter schema on file.
View your DCA partners and weekly status.
No parameter schema on file.
View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.
No parameter schema on file.
Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress
No parameter schema on file.
Generate a new secp256k1 signing keypair for Pillar smart wallet direct operations.
No parameter schema on file.
Unlock a signing key for Pillar direct operations.
No parameter schema on file.
Lock the signing key, clearing sensitive data from memory.
No parameter schema on file.
Show signing key info: pubkey, smart wallet, lock status, and all stored keys.
No parameter schema on file.
Create or increase a leveraged sBTC position (up to 1.5x) on your Pillar smart wallet.
No parameter schema on file.
Close or reduce your leveraged sBTC position. Agent-signed, no browser needed.
No parameter schema on file.
Earn yield on your Bitcoin. Supply sBTC from your Pillar smart wallet to Zest Protocol.
No parameter schema on file.
Send sBTC from your Pillar smart wallet to a recipient.
No parameter schema on file.
Configure auto-compound for your Pillar wallet.
No parameter schema on file.
View your Pillar smart wallet balances (STX, sBTC, aeUSDC) and Zest position.
No parameter schema on file.
Withdraw sBTC collateral from Zest on the Pillar smart wallet.
No parameter schema on file.
Add a backup admin address to your Pillar smart wallet for recovery purposes.
No parameter schema on file.
Create a new Pillar smart wallet for agent direct operations.
No parameter schema on file.
Invite a DCA partner by email or wallet address.
No parameter schema on file.
View your DCA partners and weekly status.
No parameter schema on file.
View the DCA streak leaderboard. Shows top partnerships by streak length, and highlights your entry if you have one.
No parameter schema on file.
Check your DCA schedule status. Shows all active DCA schedules (up to 10) with chunk progress
No parameter schema on file.
Get a boost quote showing projected leverage, LTV, and swap details.
No parameter schema on file.
Resolve a recipient before sending. Resolves BNS names (.btc) via backend,
No parameter schema on file.
Stack STX from your Pillar smart wallet via Fast Pool or Stacking DAO.
No parameter schema on file.
Revoke Fast Pool STX delegation from your Pillar smart wallet.
No parameter schema on file.
Check stacking status for your Pillar smart wallet.
No parameter schema on file.
Sign structured Clarity data using SIP-018 standard.
No parameter schema on file.
Verify a SIP-018 signature and recover the signer
No parameter schema on file.
Compute the SIP-018 message hash without signing.
No parameter schema on file.
Sign a plain text message using the Stacks message signing format.
No parameter schema on file.
Verify a Stacks message signature and recover the signer
No parameter schema on file.
Sign a plain text message using Bitcoin message signing.
No parameter schema on file.
Verify a Bitcoin message signature (BIP-137 or BIP-322) and recover or confirm the signer.
No parameter schema on file.
Sign a raw 32-byte digest with Schnorr (BIP-340) using the wallet
No parameter schema on file.
Verify a BIP-340 Schnorr signature over a 32-byte digest.
No parameter schema on file.
Sign a Nostr event (NIP-01) using BIP-340 Schnorr.
No parameter schema on file.
No parameter schema on file.
Stop autonomous yield hunting. Stops the background process that monitors and deposits sBTC. Your existing Zest positions remain untouched.
No parameter schema on file.
Get current yield hunter status. Shows: - Whether yield hunting is active - Current configuration - Statistics (checks run, deposits made) - Recent activity logs - Current Zest position
No parameter schema on file.
Configure yield hunter settings. Adjust the deposit threshold, reserve, or check interval. Changes take effect on the next check cycle.
No parameter schema on file.
Get the BTC balance for a Bitcoin address.
No parameter schema on file.
Get current Bitcoin fee estimates for different confirmation targets.
No parameter schema on file.
List all UTXOs (Unspent Transaction Outputs) for a Bitcoin address.
No parameter schema on file.
Transfer BTC to a recipient address.
No parameter schema on file.
Get cardinal UTXOs (safe to spend - no inscriptions or runes).
No parameter schema on file.
Get ordinal UTXOs (contain inscriptions or runes - do not spend).
No parameter schema on file.
Get all inscriptions owned by a Bitcoin address.
No parameter schema on file.
Get market ticker data from Bitflow DEX. Returns price, volume, and liquidity data for all trading pairs. This endpoint does NOT require an API key. Note: Bitflow is only available on mainnet.
No parameter schema on file.
Get all available tokens for swapping on Bitflow. Returns the list of tokens that can be swapped on Bitflow DEX. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Get possible swap target tokens for a given input token on Bitflow. Returns all tokens that can be received when swapping from the specified token. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Get a swap quote from Bitflow DEX. Returns the expected output amount and best route for swapping tokens. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Get all possible swap routes between two tokens on Bitflow. Returns all available routes for swapping from tokenX to tokenY, including multi-hop routes through intermediate tokens. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Execute a token swap on Bitflow DEX. Swaps tokenX for tokenY using Bitflow
No parameter schema on file.
Get or create a Bitflow Keeper contract for automated swaps. Keeper contracts enable scheduled/automated token swaps. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Create an automated swap order via Bitflow Keeper. Creates a pending order that will be executed by the Keeper service. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Get details of a Bitflow Keeper order. Retrieves the status and details of a specific order. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Cancel a Bitflow Keeper order. Cancels a pending order before execution. No API key required — uses public endpoints (500 req/min). Note: Bitflow is only available on mainnet.
No parameter schema on file.
Get Bitflow Keeper user info and orders. Retrieves user
No parameter schema on file.
Resolve a .btc domain name to its Stacks address.
No parameter schema on file.
Get the BNS domain names owned by an address.
No parameter schema on file.
Get detailed information about a BNS domain name.
No parameter schema on file.
Check if a BNS domain name is available for registration.
No parameter schema on file.
Get the registration price for a BNS domain name.
No parameter schema on file.
List all BNS domains owned by an address.
No parameter schema on file.
Register a BNS domain name in a single transaction using name-claim-fast.
No parameter schema on file.
Preorder a BNS domain name (step 1 of 2-step registration).
No parameter schema on file.
Register a BNS domain name after preorder is confirmed. This is step 2 of a 2-step process.
No parameter schema on file.
Call a function on a Stacks smart contract. Signs and broadcasts the transaction. For typed arguments, use objects like {type:
No parameter schema on file.
Deploy a Clarity smart contract to the Stacks blockchain.
No parameter schema on file.
Check the status of a Stacks transaction by its txid.
No parameter schema on file.
Call a read-only function on a smart contract (no signing required).
No parameter schema on file.
Get a swap quote from ALEX DEX. Returns the expected output amount for swapping tokenX to tokenY. Use full contract IDs for tokens (e.g.,
No parameter schema on file.
Execute a token swap on ALEX DEX. Swaps tokenX for tokenY using the ALEX AMM. Use full contract IDs for tokens. Note: ALEX DEX is only available on mainnet.
No parameter schema on file.
Get liquidity pool information from ALEX DEX. Returns reserve balances and pool details for a token pair. Note: ALEX DEX is only available on mainnet.
No parameter schema on file.
List all available trading pools on ALEX DEX. Discovers all token pairs that can be swapped directly. Returns pool ID, token pair, and factor (fee tier) for each pool. Use this to find which tokens can be swapped before calling alex_swap. Note: ALEX DEX is only available on mainnet.
No parameter schema on file.
No parameter schema on file.
Get user
No parameter schema on file.
Supply assets to Zest Protocol (v0-4-market). Deposits assets and adds them as collateral in one atomic operation. The supplied assets earn yield AND provide borrowing power. You can use the asset symbol (e.g.,
No parameter schema on file.
Withdraw assets from Zest Protocol (v0-4-market). Removes collateral and redeems for underlying assets in one atomic operation. You can use the asset symbol (e.g.,
No parameter schema on file.
Borrow assets from Zest Protocol (v0-4-market). Borrows assets against your supplied collateral. Ensure you have sufficient collateral to maintain a healthy LTV. You can use the asset symbol (e.g.,
No parameter schema on file.
No parameter schema on file.
Repay borrowed assets to Zest Protocol (v0-4-market). Repays borrowed assets plus accrued interest. You can use the asset symbol (e.g.,
No parameter schema on file.
No parameter schema on file.
Execute an x402 API endpoint. Payment is handled automatically. Supported sources: - x402.biwas.xyz (default): Use path like
No parameter schema on file.
No parameter schema on file.
Register a new agent identity on-chain using ERC-8004 identity registry.
No parameter schema on file.
Get agent identity information from ERC-8004 identity registry.
No parameter schema on file.
Submit feedback for an agent using ERC-8004 reputation registry.
No parameter schema on file.
Get aggregated reputation summary for an agent from ERC-8004 reputation registry.
No parameter schema on file.
Request third-party validation for an agent using ERC-8004 validation registry.
No parameter schema on file.
Get the status of a validation request using ERC-8004 validation registry.
No parameter schema on file.
Get validation summary for an agent using ERC-8004 validation registry.
No parameter schema on file.
⛔ DEPRECATED — do not use. The sponsored (relay) inbox send has been removed.
No parameter schema on file.
List all NFTs owned by an address.
No parameter schema on file.
Get metadata for a specific NFT (SIP-016).
No parameter schema on file.
Transfer an NFT (SIP-009) to a recipient address.
No parameter schema on file.
Get the current owner of a specific NFT.
No parameter schema on file.
Get information about an NFT collection.
No parameter schema on file.
Get the transfer history of NFTs in a collection.
No parameter schema on file.
Get the current weather in a location
No parameter schema on file.
No parameter schema on file.
Get list of popular OpenRouter models with capabilities and context lengths. Use this to choose the right model for your use case. For latest pricing, check openrouter.ai/models
No parameter schema on file.
Get the current weather in a location
No parameter schema on file.
Get the current weather in a location
No parameter schema on file.
Get the wallet
No parameter schema on file.
Calculate the total cost (in satoshis) for creating an inscription.
No parameter schema on file.
Create a Bitcoin inscription - STEP 1: Broadcast commit transaction.
No parameter schema on file.
Complete a Bitcoin inscription - STEP 2: Broadcast reveal transaction.
No parameter schema on file.
Get inscription content from a Bitcoin reveal transaction.
No parameter schema on file.
Get current STX fee estimates for different priority levels.
No parameter schema on file.
Get detailed account information including nonce and balance.
No parameter schema on file.
Get transaction history for an account.
No parameter schema on file.
Get information about a specific block.
No parameter schema on file.
Get pending transactions in the mempool.
No parameter schema on file.
Get information about a smart contract including its ABI.
No parameter schema on file.
Get events emitted by a smart contract.
No parameter schema on file.
Get the current status of the Stacks network.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Get the sBTC balance for a wallet address.
No parameter schema on file.
Transfer sBTC tokens to a recipient address. sBTC uses 8 decimals (same as Bitcoin). Example: To send 0.001 sBTC, use amount
No parameter schema on file.
Initiate an sBTC peg-out to a Bitcoin L1 address. Locks (amount + maxFee) of sBTC in the sBTC protocol and creates a withdrawal request. Signers later process the request and send BTC on L1.
No parameter schema on file.
Alias for sbtc_initiate_withdrawal. Initiates an sBTC peg-out request to BTC L1.
No parameter schema on file.
Check status of an sBTC withdrawal request by requestId or initiating txid.
No parameter schema on file.
Alias for sbtc_withdrawal_status. Check the status of an sBTC peg-out (withdrawal) request.
No parameter schema on file.
Get information about how to deposit BTC to receive sBTC.
No parameter schema on file.
Get sBTC peg information including total supply and peg ratio.
No parameter schema on file.
Deposit BTC to receive sBTC on Stacks L2. This builds, signs, and broadcasts a Bitcoin transaction to the sBTC deposit address. After confirmation, sBTC tokens are minted to your Stacks address. The transaction uses your wallet
No parameter schema on file.
Check the status of an sBTC deposit transaction from Emily API.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Save a Hiro API key to ~/.aibtc/config.json for authenticated Hiro API requests. Authenticated requests get higher rate limits than public (unauthenticated) requests. Get a free API key at https://platform.hiro.so/
No parameter schema on file.
Check whether a Hiro API key is configured. Shows the key source (stored file or environment variable) and a masked preview.
No parameter schema on file.
Remove the stored Hiro API key from ~/.aibtc/config.json. If HIRO_API_KEY is set in the environment, that will still be used as a fallback.
No parameter schema on file.
Point all Stacks API requests at a custom node instead of the default Hiro API. Use this if you run your own stacks-blockchain-api node (default port 3999) or use a third-party provider. The URL should serve the same /v2/ and /extended/v1/ endpoints as api.hiro.so. Example: http://localhost:3999
No parameter schema on file.
Show the current Stacks API URL being used for blockchain queries. Indicates whether it
No parameter schema on file.
Remove the custom Stacks API URL and revert to the default Hiro API (api.mainnet.hiro.so or api.testnet.hiro.so).
No parameter schema on file.
Check the currently running MCP server version and compare with the latest published version on npm. Use this to detect if you
No parameter schema on file.
Get current Proof of Transfer (PoX) cycle information.
No parameter schema on file.
Check if an address is currently stacking STX.
No parameter schema on file.
Lock STX for stacking to earn BTC rewards. Requires a Bitcoin address (hash) for receiving rewards.
No parameter schema on file.
Extend an existing stacking lock period.
No parameter schema on file.
Get the balance of any SIP-010 token for a wallet address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID: address.contract-name
No parameter schema on file.
Transfer any SIP-010 token to a recipient address. Supports well-known tokens by symbol: sBTC, USDCx, ALEX, DIKO Or use the full contract ID.
No parameter schema on file.
Get metadata for a SIP-010 token (name, symbol, decimals, supply).
No parameter schema on file.
List all fungible tokens owned by an address.
No parameter schema on file.
Get the top holders of a SIP-010 token.
No parameter schema on file.
Transfer STX tokens to a recipient address. Signs and broadcasts the transaction. Example: To send 2 STX, use amount
No parameter schema on file.
Broadcast a pre-signed Stacks transaction to the network.
No parameter schema on file.
Get the agent
No parameter schema on file.
Get the STX balance for a wallet address.
No parameter schema on file.
Create a new wallet for the agent with a generated BIP39 24-word mnemonic. The wallet is encrypted locally and stored in ~/.aibtc/. IMPORTANT: Save the mnemonic securely - it will only be shown once!
No parameter schema on file.
Import an existing wallet for the agent using a BIP39 mnemonic phrase. The wallet is encrypted locally and stored in ~/.aibtc/.
No parameter schema on file.
Unlock the agent
No parameter schema on file.
Lock the agent
No parameter schema on file.
List all wallets available for the agent to use.
No parameter schema on file.
Switch to a different wallet. Note: The new wallet will need to be unlocked before use.
No parameter schema on file.
Permanently delete a wallet. WARNING: This cannot be undone! Make sure you have backed up your mnemonic.
No parameter schema on file.
Export the mnemonic phrase for a wallet. WARNING: Only use this in a secure environment! Anyone with the mnemonic can access your funds.
No parameter schema on file.
Change the password for a wallet
No parameter schema on file.
Set how long the agent
No parameter schema on file.
Get the agent
No parameter schema on file.
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Stx402 Agent or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (67 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| stx402_migration_notice | no tags | |
| get_wallet_info | no tags | |
| get_stx_balance | no tags | |
| transfer_stx | no tags | |
| call_contract | no tags | |
| deploy_contract | no tags | |
| broadcast_transaction | no tags | |
| get_transaction_status | no tags | |
| call_read_only_function | no tags | |
| list_x402_endpoints | no tags | |
| execute_x402_endpoint | no tags | |
| wallet_create | no tags | |
| wallet_import | no tags | |
| wallet_unlock | no tags | |
| wallet_lock | no tags | |
| wallet_list | no tags | |
| wallet_switch | no tags | |
| wallet_delete | no tags | |
| wallet_export | no tags | |
| wallet_set_timeout | no tags | |
| wallet_status | no tags | |
| alex_get_swap_quote | no tags | |
| alex_swap | no tags | |
| alex_get_pool_info | no tags | |
| alex_list_pools | no tags | |
| zest_list_assets | no tags | |
| zest_get_position | no tags | |
| zest_supply | no tags | |
| zest_withdraw | no tags | |
| zest_borrow | no tags | |
| zest_repay | no tags | |
| lookup_bns_name | no tags | |
| reverse_bns_lookup | no tags | |
| get_bns_info | no tags | |
| check_bns_availability | no tags | |
| get_bns_price | no tags | |
| list_user_domains | no tags | |
| sbtc_get_balance | no tags | |
| sbtc_transfer | no tags | |
| sbtc_get_deposit_info | no tags | |
| sbtc_get_peg_info | no tags | |
| get_token_balance | sensitive-source | sensitive-source: keyword "get_token" |
| transfer_token | no tags | |
| get_token_info | sensitive-source | sensitive-source: keyword "get_token" |
| list_user_tokens | no tags | |
| get_token_holders | sensitive-source | sensitive-source: keyword "get_token" |
| get_nft_holdings | no tags | |
| get_nft_metadata | no tags | |
| transfer_nft | no tags | |
| get_nft_owner | no tags | |
| get_collection_info | no tags | |
| get_nft_history | no tags | |
| get_pox_info | no tags | |
| get_stacking_status | no tags | |
| stack_stx | no tags | |
| extend_stacking | no tags | |
| get_account_info | no tags | |
| get_account_transactions | no tags | |
| get_block_info | no tags | |
| get_mempool_info | no tags | |
| get_contract_info | no tags | |
| get_contract_events | no tags | |
| get_network_status | no tags | |
| scaffold_x402_endpoint | no tags | |
| scaffold_x402_ai_endpoint | no tags | |
| openrouter_integration_guide | no tags | |
| openrouter_models | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 3.0.2. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Stx402 Agent can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.