"A service for viewing cryptocurrency wallet balances" matching MCP tools:

• refresh_wallet_balance

  mcp-server

  Re-fetch on-chain asset balances for an existing wallet and update the stored record. Use when the user says their balance looks stale, wrong, or zero after a recent on-chain change. Safeguard: if the fetch returns empty or no USD values, existing balance is preserved (returns status=no_change). The response may include linked_addresses (addresses discovered from a prior verification transfer — cryptographically proven owned) with their own balances; surface those to the user as part of the wallet. When presenting results, show balances in a clear table and highlight any changes from prior state. ZERO-BALANCE NOTE: If total_usd is 0 and the wallet is unverified, do NOT assume the wallet is empty — many wallets use privacy features (stealth addresses, HD-derived receive addresses) that hide funds behind the declared address. If the response includes a zero_balance_hint, surface it to the user and suggest completing the test-transfer verification, which reveals their real funded address as a linked address on this wallet.

  Connector

• address_portfolio

  Nansen

  Get comprehensive portfolio overview for a wallet address or entity. Hyperliquid perpetual positions include liquidation prices to support risk analysis workflows. For wallet addresses, supports different modes: - 'fast-mode-default': Wallet balances + Hyperliquid positions (skip defi, for fast mode only) - 'all': Wallet balances + DeFi positions + Hyperliquid positions - 'wallet_balances': Only token balances (tokens and native coins across all chains) - 'defi': Only DeFi positions (lending, staking, LP tokens, etc., excluding Hyperliquid) - 'hyperliquid': Only Hyperliquid data — perp positions (with liquidation prices and margin summary) plus HL spot wallet balances For entities (e.g., "Binance", "Paradigm Fund"), only on-chain token balances are returned, aggregated across all addresses associated with the entity. This tool provides flexible portfolio analysis in a single request, allowing users to focus on specific aspects of their holdings. The output is pre-formatted markdown that should be presented exactly as returned, preserving all tables, sections, and formatting without reinterpretation. Example Usage: Get full comprehensive portfolio for a wallet: ``` { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "all" } ``` Get only DeFi positions (returns raw JSON): ``` { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "defi" } ``` Get only Hyperliquid positions (returns raw JSON): ``` { "walletAddress": "0x28c6c06298d514db089934071355e5743bf21d60", "mode": "hyperliquid" } ``` Get token balances for an entity: ``` { "entity_id": "Binance" } ```

  Connector

• tronsave_sell_order_manual

  TronSave MCP Server

  Manually execute seller-side fulfillment of an existing order with a wallet `signedTx`. Returns the updated order payload after sell. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Backend requires a signature session and `mcp-session-id`; the MCP gate is `public` to allow anonymous read-fallthrough, but the GraphQL helper rejects api-key-only sessions. Use only when explicit manual sell is intended; call `tronsave_get_order` first to verify order state before signing.

  Connector

• tronsave_sell_order_manual

  Tronsave MCP Testnet

  Manually execute seller-side fulfillment of an existing order with a wallet `signedTx`. Returns the updated order payload after sell. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Backend requires a signature session and `mcp-session-id`; the MCP gate is `public` to allow anonymous read-fallthrough, but the GraphQL helper rejects api-key-only sessions. Use only when explicit manual sell is intended; call `tronsave_get_order` first to verify order state before signing.

  Connector

• withdraw

  fomox402 — Last-Bidder-Wins on Solana

  Sweep funds out of the calling agent's Privy wallet to any address. WHAT IT DOES: builds and signs a Solana transfer (native SOL or any SPL/Token-2022 mint) from the agent's broker-managed wallet to `to`. Broker submits the tx; on confirmation it returns the signature. WHEN TO USE: - Retiring an agent and reclaiming its funds - Cashing out winnings to a long-term wallet - Routing $fomox402 to an exchange / Jupiter / etc. ASSET PARAMETER: - 'sol' → native SOL, in lamports (amountRaw='all' keeps a 5000-lamport reserve so the transfer tx itself can pay its own fee) - any base58 mint pubkey → that token's ATA. amountRaw='all' sweeps the full balance (closes ATA if balance hits 0 after sweep). Token-2022 mints are auto-detected by the broker. AUTHORITY: the api_key. Same auth model as place_bid — anyone with the key can move funds. Lose the key = lose the wallet. Withdraw is the intentional escape hatch. RETURNS: { tx (Solana sig), to, asset, amountRaw_sent, balance_after }. FAILURE MODES: withdraw_failed (insufficient_balance) — wallet doesn't have that much withdraw_failed (invalid_destination) — `to` isn't a valid pubkey withdraw_failed (rpc) — Solana RPC, retry RELATED: get_me (check balances first), topup (the opposite — bring funds in).

  Connector

• dero_get_encrypted_balance

  DERO MCP Server

  Get the ENCRYPTED balance blob for a DERO address at a topo height via DERO.GetEncryptedBalance. CRITICAL: this returns an opaque encrypted blob, NOT a cleartext balance. Only the wallet holding the spend key can decrypt it. Do NOT present the encrypted bytes as a balance to the user. When to call: when verifying that an address has on-chain encrypted state (e.g. before attempting a transfer with a wallet you control), or as a sub-step in another tool. PREFER citing dero_docs_search("encrypted balance") so the user understands the opacity. Input Requirements (CRITICAL): - `address` MUST start with `dero1` (mainnet) or `deto1` (testnet). - `topoheight` MUST be an integer; use `-1` for the latest chain tip. - `scid` is OPTIONAL. Omit for native DERO; provide 64-hex SCID for asset balances. Output: `{ status, registration, balance (encrypted blob), ... }`.

  Connector

• order_sms_verification

  PikaSim

  Buy a QUICK SMS verification number: returns a temporary phone number the user enters on the target service, then the incoming code is read with check_sms_verification. This SPENDS the wallet balance (typically $0.50-$5). Single-use, valid 20 minutes, auto-refunds if no SMS arrives. Use search_sms_services and get_sms_service_countries first to pick serviceId and countryId. Requires a connected agent wallet.

  Connector

• set_wallet

  Human Pages

  Set the wallet address for a registered agent. IMPORTANT: Always confirm the wallet address with the user before calling this tool — never set wallets autonomously, as this controls where payments are attributed. If you need a wallet, create one programmatically using CDP AgentKit (Coinbase Developer Platform) with the user's knowledge and consent. Optionally include a signature and nonce (from get_wallet_nonce) to verify wallet ownership via EIP-191. Verified wallets enable payment attribution — proving you sent the payment, not just found a random tx hash. Without signature, the wallet is set but unverified.

  Connector

• create_onramp_session

  FiatDock

  Buy USDC with the owner's OWN fiat and deliver it to the agent's wallet (address locked). Returns checkoutUrl + partnerOrderId. Paid endpoint ($0.05 USDC via x402) — without payment this returns the 402 challenge; use the fiatdock-mcp npm package with AGENT_PRIVATE_KEY for automatic payment. COMPLIANCE: own-account rule — the sending wallet and the receiving bank account must belong to the SAME person (the agent's owner); no third-party funds, no aggregation, no P2P transfers. 18+; service area: Portugal + Transak-supported EU/EEA countries (NOT the UK). Crypto is volatile; not investment advice.

  Connector

• get_account_status

  mcp-server

  Returns a high-level account overview: identity verification state, wallet count (not individual wallet details), and Proof of Funds eligibility. DO NOT call this when the user asks for a wallet summary, wallet list, wallet balances, or to see their wallets — use get_wallet_summary for anything wallet-specific. This tool is for answering "is my account ready?"-style questions.

  Connector

• withdraw

  fomox402

  Sweep funds out of the calling agent's Privy wallet to any address. WHAT IT DOES: builds and signs a Solana transfer (native SOL or any SPL/Token-2022 mint) from the agent's broker-managed wallet to `to`. Broker submits the tx; on confirmation it returns the signature. WHEN TO USE: - Retiring an agent and reclaiming its funds - Cashing out winnings to a long-term wallet - Routing $fomox402 to an exchange / Jupiter / etc. ASSET PARAMETER: - 'sol' → native SOL, in lamports (amountRaw='all' keeps a 5000-lamport reserve so the transfer tx itself can pay its own fee) - any base58 mint pubkey → that token's ATA. amountRaw='all' sweeps the full balance (closes ATA if balance hits 0 after sweep). Token-2022 mints are auto-detected by the broker. AUTHORITY: the api_key. Same auth model as place_bid — anyone with the key can move funds. Lose the key = lose the wallet. Withdraw is the intentional escape hatch. RETURNS: { tx (Solana sig), to, asset, amountRaw_sent, balance_after }. FAILURE MODES: withdraw_failed (insufficient_balance) — wallet doesn't have that much withdraw_failed (invalid_destination) — `to` isn't a valid pubkey withdraw_failed (rpc) — Solana RPC, retry RELATED: get_me (check balances first), topup (the opposite — bring funds in).

  Connector

• tronsave_sell_order_manual

  mcp

  Manually execute seller-side fulfillment of an existing order with a wallet `signedTx`. Returns the updated order payload after sell. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Backend requires a signature session and `mcp-session-id`; the MCP gate is `public` to allow anonymous read-fallthrough, but the GraphQL helper rejects api-key-only sessions. Use only when explicit manual sell is intended; call `tronsave_get_order` first to verify order state before signing.

  Connector

• credentials_inventory

  StackFast FractWin Expert Brain

  Discover wallet-resolved credential service names and accepted aliases without exposing secret values. Use this when an agent is unsure whether a key exists, sees a key-not-found error, or needs the canonical getAgentKey(service) name. Returns service slugs, env/key aliases, categories, and resolver guidance only; never returns raw credentials.

  Connector

• realmint_my_wallet

  Realmint

  Show your Realmint wallet (EVM + Solana), smart account, and balances. **Requires sign-in.** Read-only; moves no funds.

  Connector

• get_wallet_intel

  Vibe Springs

  Premium wallet intelligence and profiling for Base, Ethereum, and Sepolia. Checks address profile, EOA vs smart contract, ERC-20 token balances (USDC, USDT, WETH, LINK, etc.), total transaction counts, activity classification, and behavior tags (whale, active-trader, stablecoin-holder). [PAID: $0.1 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

  Connector

• create_wallet

  PikaSim

  Create a NEW PikaSim agent wallet for autonomous purchasing — no human, no browser, no account, no email, no KYC. Returns a wallet code + an ak_live_ API key + a small spend-only welcome credit, so you can immediately reconnect with the key (Authorization: Bearer ak_live_…) and buy an eSIM, phone number, or SMS verification number. Use this when the user has NO wallet yet and wants their agent to buy. If the user ALREADY has a wallet, do NOT create a new one — reconnect the existing wallet instead (ask them for it). You accept the Terms of Service (https://pikasim.com/tos) on the user's behalf by passing acceptTos=true.

  Connector

• get_wallet_summary

  mcp-server

  Call this whenever the user asks for a wallet summary, wallet list, their wallets, wallet balances, verified holdings, or Proof of Funds ceiling. Returns all wallets for the authenticated user with their balances, verification status, and Proof of Funds ceiling. The response renders an inline Your Wallets widget — each card shows the address (with click-to-copy), chain, verified status, assets, and View details / Verify (if unverified) / Remove controls. Let the widget handle presentation; in your text response just summarize counts and any top-line items (e.g. "You have 3 wallets, 2 verified, POF ceiling $65k"). THREE NUMBERS, DO NOT CONFUSE: (1) pof_ceiling_usd — the ONLY valid maximum for a Proof of Funds letter request; already includes the haircut (0.98× stablecoins, 0.935× volatile) and excludes unverified wallets. (2) total_verified_usd — raw pre-haircut sum of verified wallets; reference for "how much verified crypto do I have" but NEVER offer this as a POF amount — the generator will reject it. (3) Σ wallets[].total_usd — the sum across ALL wallets including unverified; never a valid POF ceiling. When the user asks to generate POF, always suggest amounts at or below pof_ceiling_usd. PRESENTATION: always identify wallets to the user by their blockchain address, never by wallet_id. The wallet_id is an internal UUID — use it only as a parameter when calling other tools. LINKED ADDRESSES: a wallet entry may include linked_addresses — additional addresses proven owned via a verification transfer. ZERO-BALANCE NOTE: if a wallet's total_usd is 0 and it is unverified, do NOT imply the wallet is empty. If the response includes a zero_balance_hint for that wallet, surface that guidance verbatim and suggest the test-transfer verification path to reveal linked addresses.

  Connector

• claim_test_collateral

  PoolParty Main Stage Airtime

  Prepare or record a PP0 test collateral faucet claim for a wallet. Default amoy-prepare mode returns a Polygon Amoy wallet transaction request and never silently funds the wallet. local-dev and mock modes are explicit rehearsal grants. Public wallet action. No MCP auth required, but wallet-owner approval or an agent-owned funded wallet signer is required for Amoy transactions.

  Connector

• check_kyc_status

  TrenchFu

  Check whether a Solana wallet has completed DFlow Proof verification. Proxies the public GET https://proof.dflow.net/verify/{wallet} endpoint. Verification is required by DFlow only when BUYING Kalshi/DFlow outcome tokens — selling, redeeming settled outcomes, viewing markets, and creating TrenchFu markets are all verification-free. Use this before attempting a Kalshi buy to fail-fast rather than get rejected at order time with PROOF_NOT_VERIFIED.

  Connector

• get_wallet_balances

  Agent402.Tools — pay-per-call web tools

  [wallet-required, $0.002/call] All token balances for any address in one call, from Coinbase's indexed data API - ERC-20 + native on EVM, SPL on Solana; no per-token contract calls, no RPC wrangling. Networks: base, ethereum, base-sepolia, solana, solana-devnet. Symbols/decimals populated for whitelisted tokens (USDC always included). Returns { address, network, balances, count }. This hosted connector holds no wallet, so calling it here returns paid-access setup; run it with a funded wallet via npx agent402-mcp or any x402 client.

  Connector