"How to interact with a MetaMask wallet" matching MCP tools:

• remove_walletA

  mcp-serverA

  Permanently remove a wallet from the authenticated user's account. Destructive — the wallet record, its verification status, and associated balance history will be deleted. Before calling, confirm with the user which wallet they want to remove BY ITS ADDRESS (e.g. "remove the Bitcoin wallet at bc1q...abc?") and get explicit confirmation. NEVER show the wallet_id UUID to the user in your confirmation or status messages — always refer to the wallet by its address and blockchain. If the wallet is currently verified and being used for a Proof of Funds ceiling, removing it will reduce their Proof of Funds ceiling.

  Connector

  Destructive

  No auth

• portal_get_wallet_summaryA

  SQDA

  Summarize wallet activity and fund flow with shared overview, asset movement, counterparties, evidence pivots, and follow-up filters across supported networks. COMMON USER ASKS: - EVM wallet fund-flow triage - Solana wallet activity and fee flow FIRST CHOICE FOR: - one-call wallet analysis across supported VMs - suspicious wallet triage, fund-flow direction, counterparties, and next evidence pivots before drilling into raw records WHEN TO USE: - You want a single high-level answer about what one wallet has been doing and where value appears to move. - You want inbound/outbound flow, activity and asset-movement counterparties, largest movements within each asset, and exact next pivots before drilling into raw transactions or fills. - The user asks to investigate a suspicious wallet, stolen-funds path, exploit counterparty, or incident address. DON'T USE: - You need every raw record with full chain-specific fields and no summarization. EXAMPLES: - EVM wallet fund-flow triage: {"network":"base-mainnet","address":"0xabc...","timeframe":"24h"} - Solana wallet activity and fee flow: {"network":"solana-mainnet","address":"Vote111...","timeframe":"6h"}

  ConnectorNo auth

• check_balanceA

  PikaSimA

  Returns the prepaid spending balance of the connected PikaSim agent wallet, in USD. Read-only; makes no changes. Call this before purchase_esim or purchase_phone_plan to confirm sufficient funds, or any time you need the current balance. Requires a connected agent wallet (OAuth or ak_live_ key). If no wallet is connected, the result explains how to connect one.

  ConnectorNo auth

• create_campaign_quoteA

  PostAgent — Print and MailA

  Quote ONE bulk send to MANY recipients (up to 500): a single template or static document, fulfilled through PostAgent's campaign workflow. Price is an inclusive customer-facing total, locked for 15 minutes. Payment is x402 ONLY. IMPORTANT — KYC WALL: campaigns require the paying wallet to be identity-verified with PostAgent. Verification is operator-run, not self-serve: until the wallet is verified this tool returns `kyc_required` (403). Do not retry the same wallet — instead either mail recipients individually with create_mail_quote, or request campaign access at https://interpretai.tech/contact (this URL is also returned in the 403's details.contactUrl) to get the wallet enabled. Usage once the wallet is verified: upload a template with create_template (using {{fields}}) or a finished letter with create_letter, then call this with `recipients` (each `to` a US address, plus per-recipient `mergeVariables` for templates) and the `payerWallet` that will pay the quote. The print partner validates every recipient address after payment; failed recipients are excluded and their share refunded (processed manually). Track via get_campaign_status.

  ConnectorNo auth

• get_account_statusA

  mcp-serverA

  Returns a high-level account overview of where the user stands in getting ready to buy real estate with crypto: 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 and for resuming setup: the response includes activation.next_action — the single correct next step for this user's state. The response renders an inline progress widget (checklist + one next-step CTA); keep your text to a short summary and let the widget carry the presentation.

  ConnectorNo auth

• get_wallet_summaryA

  mcp-serverA

  Call this whenever the user asks for a wallet summary, wallet list, their wallets, wallet balances, verified holdings, or Proof of Funds ceiling — i.e. how much verified crypto they can show for a real estate offer. Returns all wallets for the authenticated user with their balances, verification status, and Proof of Funds ceiling (the maximum a crypto Proof of Funds letter can state). 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. ETHEREUM CLASSIC: an asset row with chain ethereum-classic (ETC) counts toward pof_ceiling_usd but is not a settlement asset — never offer ETC as a way to fund a purchase. 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. BITCOIN FULL-WALLET NOTE: a verified Bitcoin wallet entry may carry full_wallet_hint (no extended public key linked yet — only the verified address and transfer-proven addresses are counted) or xpub_linked: true with an xpub_scan summary (every derived address counted). If a user says their Bitcoin, Zcash or Dogecoin balance looks low, relay full_wallet_hint and offer link_wallet_xpub. ZCASH: a Zcash wallet entry carries transparent_only_hint — only transparent (t1…) balances are verified and counted; relay it before the user starts verification if their ZEC may be shielded. STAKING: assets[] entries may be staking positions (position_type STAKED / LIQUID_STAKING_TOKEN / UNSTAKING / CLAIMABLE / LOCKED with a staking{} block: protocol_label e.g. "Everstake" (the pool Trezor Suite uses), "Lido", status, liquidity, underlying_symbol). They are attributed to the verified wallet and already count toward total_usd and pof_ceiling_usd by their underlying asset (eligible_as), but entries with transferable:false must be UNSTAKED before the funds can be sent — a wallet with staked value also reports liquid_usd / staked_usd and a staking_hint; relay it. Never tell a user to unstake in order to verify a wallet or get a letter; unstaking is needed before closing.

  ConnectorNo auth

• create_campaign_quoteA

  PostAgentA

  Quote ONE bulk send to MANY recipients (up to 500): a single template or static document, fulfilled through PostAgent's campaign workflow. Price is an inclusive customer-facing total, locked for 15 minutes. Payment is x402 ONLY. IMPORTANT — KYC WALL: campaigns require the paying wallet to be identity-verified with PostAgent. Verification is operator-run, not self-serve: until the wallet is verified this tool returns `kyc_required` (403). Do not retry the same wallet — instead either mail recipients individually with create_mail_quote, or request campaign access at https://interpretai.tech/contact (this URL is also returned in the 403's details.contactUrl) to get the wallet enabled. Usage once the wallet is verified: upload a template with create_template (using {{fields}}) or a finished letter with create_letter, then call this with `recipients` (each `to` a US address, plus per-recipient `mergeVariables` for templates) and the `payerWallet` that will pay the quote. The print partner validates every recipient address after payment; failed recipients are excluded and their share refunded (processed manually). Track via get_campaign_status.

  ConnectorNo auth

• create_campaign_quoteA

  PostAgentA

  Quote ONE bulk send to MANY recipients (up to 500): a single template or static document, fulfilled through PostAgent's campaign workflow. Price is an inclusive customer-facing total, locked for 15 minutes. Payment is x402 ONLY. IMPORTANT — KYC WALL: campaigns require the paying wallet to be identity-verified with PostAgent. Verification is operator-run, not self-serve: until the wallet is verified this tool returns `kyc_required` (403). Do not retry the same wallet — instead either mail recipients individually with create_mail_quote, or request campaign access at https://interpretai.tech/contact (this URL is also returned in the 403's details.contactUrl) to get the wallet enabled. Usage once the wallet is verified: upload a template with create_template (using {{fields}}) or a finished letter with create_letter, then call this with `recipients` (each `to` a US address, plus per-recipient `mergeVariables` for templates) and the `payerWallet` that will pay the quote. The print partner validates every recipient address after payment; failed recipients are excluded and their share refunded (processed manually). Track via get_campaign_status.

  ConnectorNo auth

• quantum_artificer_infoA

  quantum-artificerA

  FREE. Full catalog of Quantum Artificer: the 5 domains, their operations, input-spec shapes, limits, and prices. Call this first to learn how to build the `spec` for the paid compute tools. No wallet needed.

  ConnectorNo auth

• get_wallet_balancesA

  AaveA

  v4 only. The tokens a wallet actually holds that v4 can take, per token and summed across chains, with 'perChain' saying where each sits, plus the best supply APY and lowest borrow APY the protocol currently offers on that token. This is the wallet, not a position: nothing here is supplied or borrowed yet, and the rates alongside a balance are what Aave would pay or charge, not what the wallet is earning. Start a 'what should I do with what I have' question here and a 'how is my position doing' question at get_user_summary. Omit chainId to cover every chain v4 serves, stated under 'chainsCovered'. Zero balances are left out.

  ConnectorNo auth

• get_wallet_balancesA

  Aave MCPA

  v4 only. The tokens a wallet actually holds that v4 can take, per token and summed across chains, with 'perChain' saying where each sits, plus the best supply APY and lowest borrow APY the protocol currently offers on that token. This is the wallet, not a position: nothing here is supplied or borrowed yet, and the rates alongside a balance are what Aave would pay or charge, not what the wallet is earning. Start a 'what should I do with what I have' question here and a 'how is my position doing' question at get_user_summary. Omit chainId to cover every chain v4 serves, stated under 'chainsCovered'. Zero balances are left out.

  ConnectorNo auth

• prepare_consult_domain_expertA

  TasteA

  Get a humantaste.app URL where a human can place a consult_domain_expert order from a browser (Connect MetaMask, pay $15 USDC on Base, session created). Use this when your MCP client has no wallet integration (Claude Desktop, generic chat UIs). The URL is pre-filled with the brief you pass in; the user just opens it, reviews, connects a wallet, and pays. Returns the payment URL and the price. Free.

  ConnectorNo auth

• prepare_consult_domain_expertA

  TasteA

  Get a humantaste.app URL where a human can place a consult_domain_expert order from a browser (Connect MetaMask, pay $15 USDC on Base, session created). Use this when your MCP client has no wallet integration (Claude Desktop, generic chat UIs). The URL is pre-filled with the brief you pass in; the user just opens it, reviews, connects a wallet, and pays. Returns the payment URL and the price. Free.

  ConnectorNo auth

• inspect_walletA

  Autosophia Solana LensA

  One-call profile of a Solana wallet: SOL balance, non-zero SPL holdings, activity window, failure rate, account age, and whether it is a program. Use when you need to judge a counterparty, monitor a treasury, or research a wallet before interacting with it. $0.01 per call in USDC on Solana. Typically returns in under 2s. Read-only. address: Solana wallet address, e.g. Ezk5bEX4VbASmPMdEAvSdtLcW5Dmsgjdy5mdctKkNo1Q

  ConnectorNo auth

• preflight_bountyA

  DeskCrewA

  Free pre-check before paying to enter a bounty: is the row open and funded, does your wallet match the payout chain, do you already have a live entry there, and how much knowledge-base coverage exists to ground an answer in. Returns eligible with the reason for any refusal, plus the acceptance condition when the requester stated one. Costs nothing and changes nothing. [free]

  ConnectorNo auth

• updateWalletA

  AgoreanA

  Move your profile to a new wallet address (key migration, or a compromised wallet key). Needs your API key, a signed challenge from getChallenge (`challenge: { challenge_id, signature }`, recovery key) AND `wallet_proof` signed by the new wallet's key (purpose update_wallet, subject = your profile_id); missing either is refused. A wallet already registered to another profile is a conflict. Takes effect for future trades: your active listings are paid to the new wallet from now on, and purchases that settled to the old address stay verified. The move is one transaction — it either happens completely or not at all — and calling it again with the wallet you already have is not an error: it re-checks the history window and the listings and reports what it repointed. No seller-written text in the reply.

  ConnectorNo auth

• pump_devA

  MAD SynapseA

  A creator wallet's launch history: launches, graduation rate, launch cadence, how fast the dev sells, verdict. Looks up every token the wallet created since recording began and replays the dev's own trades on its 15 most recent launches. When to use: For the creator of a token; pass the dev wallet, not the mint (pump_token (callable here by name) reports the dev of a mint). Price: $0.01 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for invalid input or an upstream failure (not charged).

  ConnectorNo auth

• pump_devA

  MAD Synapse · Pump & LPA

  A creator wallet's launch history: launches, graduation rate, launch cadence, how fast the dev sells, verdict. Looks up every token the wallet created since recording began and replays the dev's own trades on its 15 most recent launches. When to use: For the creator of a token; pass the dev wallet, not the mint (pump_token reports the dev of a mint). Price: $0.01 per call (10 free/day; after that a payment-required result lists x402 options). Errors: returns isError with a message for invalid input or an upstream failure (not charged).

  ConnectorNo auth

• payments_how_it_worksA

  Focxle: AI governance for B2B deals between agentsA

  Explains how the payment rail works for agents: paying from your own wallet with no account, wallets we manage, spend mandates, reputation, receipts and intent enforcement. Call this first if you are new to the wallet_* and data_* tools.

  ConnectorNo auth

• wallet_exposureA

  hostdefi-x402A

  PAID ($0.10/call). Wallet risk-exposure read for a Solana wallet: its largest holdings graded through the full verdict path, exposure counts by risk tier, and a rug-ledger symbol cross-check. Holdings exposure heuristics — NOT AML attribution or sanctions screening. Call once WITHOUT x402_payment to receive the x402 payment requirements (an `accepts` array); pay one of them with any x402 client/wallet, then call again with `x402_payment` set to the base64 X-PAYMENT payload. You are only charged when a result actually comes back.

  ConnectorNo auth

• submit_auth_verifyA

  metalendA

  Exchange a signed SIWE challenge message (from get_auth_challenge) for a JWT scoped to that wallet. The returned `jwt` must be passed explicitly as the `jwt` argument to submit_deposit/submit_withdrawal/submit_config for that same wallet — this server does not cache or store it. The JWT is only valid for the walletAddress that produced the signature; using it for a different wallet's write call will be rejected upstream. Reuse the same jwt for subsequent write calls to this wallet instead of re-authenticating every time — the response's `expiresAt` (decoded from the JWT's own exp claim) says how long it's good for. Rate limited to 5 calls/minute per caller, no more than one call every 12s.

  ConnectorNo auth