Skip to main content
Glama
650,527 tools. Updated 2026-10-14 05:05

"How to retrieve wallet transactions" matching MCP tools:

  • 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
  • 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
  • Set the primary ENS name (reverse resolution) for a wallet address. This controls what name is displayed when someone looks up your Ethereum address. For example, instead of seeing "0x1234...abcd", they'd see "myname.eth". Requirements: - You must own or control the ENS name - The name's ETH address record must point to your wallet - Only the wallet owner can set their own primary name When a user says "set my primary name" / "make X my primary", JUST call this tool — it bundles BOTH transactions (set the ETH address record + set the reverse record) into a single sign-card. Do NOT also call set_ens_records separately for this. After the user signs, verify it landed with get_primary_name. Only one primary name per address — setting a new one replaces the previous.
    Connector
    Destructive
    No auth
  • 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
  • Move a little USDC from the trading subaccount back to the WALLET when the wallet is at or below $0.55 — just enough to restore the $0.95 gas reserve that deposit/withdraw transactions need. Only the gas reserve, only to the account's own wallet; it cannot send funds anywhere else. Use after a transaction fails for lack of gas.
    ConnectorNo auth
  • Move a little USDC from the trading subaccount back to the WALLET when the wallet is at or below $0.55 — just enough to restore the $0.95 gas reserve that deposit/withdraw transactions need. Only the gas reserve, only to the account's own wallet; it cannot send funds anywhere else. Use after a transaction fails for lack of gas.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server for indexing and searching local text files using late-interaction retrieval (ColBERT-style MaxSim), enabling token-level relevance matching.
    2
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    MIT

Matching MCP Connectors

  • Import a bank CSV, categorise it, summarise it per currency and reconcile it against your expenses.

  • Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.

  • Charges the Netfluid wallet's tokenised Visa/mastercards. The funds received from the card will remain in the Netfluid account_fk balance until transferred, see wallet_transfer. Only tokenised cards can be charged, use payment_3d_secure_link, when wallet_visa_mastercard_card_list returns empty in order to tokenize the card. Use wallet_visa_mastercard_card_list to retrieve the `wallet_card_id` Minimum amount is 1 ZAR. Merchant fees (3.5%) plus Netfluid Card Deposit fees (2.5%) will be deducted from the amount received. Always set the amount to charge at least 6% more than what's required in the wallet. @param wallet_fk: The Netfluid wallet_fk @param pin: The Netfluid wallet PIN @param wallet_card_id: The Netfluid tokenised card id, use wallet_visa_mastercard_card_list to retrieve this id. @param amount: The amount in ZAR to charge the card, must be 2 decimals. @param account_fk: The Netfluid account_fk into which the funds will be deposited, if 0 the system will select the first available ZAR account. On completion, use wallet_transfer to transfer funds to the paywall wallet. @return: a json object, containing the results in the "values" object
    ConnectorNo auth
  • Query raw Tron transactions: native TRX transfers, TRC-10 asset transfers, TriggerSmartContract calls by contract and method, or any contract type, with optional inline logs and internal transactions. COMMON USER ASKS: - Recent native TRX transfers - USDT transfer calls in a block window - TRX sent from one wallet FIRST CHOICE FOR: - native TRX transfers, TRC-10 transfers, and smart-contract calls on Tron - who sent TRX to an address on Tron, or which wallets called a Tron contract WHEN TO USE: - You need raw Tron transaction records with sender, recipient, amount in TRX, fee, energy, and success. - You want native TRX transfers to or from a wallet in a bounded window. - You want calls to a Tron contract such as USDT filtered by method (transfer, approve) or caller. - You want TRC-10 asset transfers by asset id. DON'T USE: - You need TRC-20 token events; those are logs, so use portal_tron_query_logs. - You need an Ethereum-compatible network; use portal_evm_query_transactions. EXAMPLES: - Recent native TRX transfers: {"network":"tron-mainnet","timeframe":"5m","kind":"transfer","limit":20} - USDT transfer calls in a block window: {"network":"tron-mainnet","from_block":84000000,"to_block":84000010,"contract_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"method":"transfer","limit":20} - TRX sent from one wallet: {"network":"tron-mainnet","timeframe":"1h","kind":"transfer","from_addresses":["TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t"],"limit":20}
    ConnectorNo auth
  • Get transaction history for a specific account with running balance. Shows transactions in reverse chronological order with a running balance column, useful for seeing how the balance changed over time. By default, only transactions dated **today or earlier** are returned — this keeps the running-balance trail anchored to the live ``current_balance``. Pass ``include_scheduled=True`` to also see future-dated rows (e.g. recurring transactions the cron will spawn); when scheduled rows are included, the running-balance walk anchors at the projected balance (``current_balance`` plus the sum of unapplied future impacts) so the math still reconciles, and each future row carries an ``is_scheduled: True`` flag. Args: account_id: Account to show history for limit: Maximum transactions to return (default 50, max 200) include_scheduled: When False (default), filter out future-dated rows. When True, include them and walk from the projected balance. Returns: Account info and transaction history with running balances. Response includes ``include_scheduled`` so callers know which view they got and ``projected_balance`` when scheduled rows are included.
    ConnectorAPI key
  • Retrieve a prepaid card you own: full card number, CVV, expiry, live balance. Owner-verified (0.01 USDC ownership proof; the paying wallet must be the card's buyer).
    ConnectorNo auth
  • Recent transactions for an address — The latest transactions for a Base address — hash, time, from/to, ETH value, success — via Covalent. For agents tracking what a wallet is doing. Required input: address. Priced $0.03 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.
    ConnectorNo auth
  • Check whether a wallet can claim BASE167. The token cannot be bought FROM THE PROJECT -- no sale, no presale, no allocation -- only claimed, and only by wallets with 167 or more transactions on Base mainnet. It does trade on the open market; the project neither sells it nor quotes a price. Returns eligibility, the transaction count, and the transaction to send if eligible. It does NOT return the claim amount: the decay curve moves it with every claim, so read calculateReward(claimCount()) on chain rather than quoting a figure. A wallet that has ALREADY claimed is reported as ineligible with no transaction, so never treat a refusal here as a reason to retry: the claim is one per wallet forever. This returns an UNSIGNED transaction ({chainId, to, data, value}) plus a short-lived voucher. This service never signs for the user and never holds keys. The user must approve and send the transaction from their own wallet. Once mined it CANNOT be undone.
    ConnectorNo auth
  • Builds an unsigned transaction blueprint for creating a borrow auction — you post collateral and ask lenders to compete to lend against it — including the prerequisite collateral approval. Every term is yours to set: which collateral and how much, which loan token and how much, the maximum repayment you will accept, the loan duration, how long the auction runs, and the bid step. This tool encodes what you specify and warns about consequences; it does not propose terms, rates or a loan size. Lenders bid DOWN from your maximum repayment, so max_repayment is your worst acceptable price — set it too low and the auction may attract no bids. Returns an unsigned transaction blueprint for the requested intent. The user is responsible for reviewing, signing, and broadcasting via their own wallet. Aletheia does not hold keys or dispatch transactions.
    ConnectorNo auth
  • Native balance (with USD), transaction count, contract or wallet, ENS name — for any address on 17 EVM chains at once or one chain. Reads straight from each chain's RPC. chain="all" checks every supported chain in parallel and returns only where the address has balance, transactions or code — the quick "where is this wallet active" answer. When to use: For EVM addresses; for Solana wallets use wallet_holdings. Price: $0.002 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
  • Prediction market summary metrics for a Polygon wallet. **When to use:** - First wallet-level Polymarket tool for a quick trader overview. - Use before detailed address trades/PnL when the user asks for a general wallet profile, activity summary, or whether a wallet is active on Polymarket. **Key fields:** - `Markets Traded` and `Markets Won` are lifetime counts; `Win Rate` is won / traded. - `Total PnL USD` = realized + unrealized. - `First Seen` and `Wallet Age (Days)` show how long the wallet has been active on Polymarket. **Pitfalls:** - The API gives no trade count, volume, or ROI here. Do not state them. For per-market cost and proceeds use `prediction_market_address_pnl`. - Blank PnL fields mean unavailable data, not zero.
    ConnectorNo auth
  • Prediction market summary metrics for a Polygon wallet. **When to use:** - First wallet-level Polymarket tool for a quick trader overview. - Use before detailed address trades/PnL when the user asks for a general wallet profile, activity summary, or whether a wallet is active on Polymarket. **Key fields:** - `Markets Traded` and `Markets Won` are lifetime counts; `Win Rate` is won / traded. - `Total PnL USD` = realized + unrealized. - `First Seen` and `Wallet Age (Days)` show how long the wallet has been active on Polymarket. **Pitfalls:** - The API gives no trade count, volume, or ROI here. Do not state them. For per-market cost and proceeds use `prediction_market_address_pnl`. - Blank PnL fields mean unavailable data, not zero.
    ConnectorNo auth
  • How many transactions has this address sent? — The next nonce for any Base address, plus its ETH balance and whether it is a contract. The count means different things either side of that line — transactions sent for a wallet, contracts deployed for a contract — so both are reported under their own name instead of one ambiguous number. What you need before building a transaction, or to tell a fresh address from a used one. Required input: address. Priced $0.002 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.
    ConnectorNo auth
  • What has this NEAR account been doing? — Recent history of a NEAR account, summed up: transactions signed and received, failures, NEAR sent and received, token flows in and out per token, the contracts it calls most, who it deals with most, and signals (inactive, failing, receive-only). One-line summary plus the last 10 transactions. Reads the NearBlocks indexer; limit sets how many recent transactions (default 25). Required input: account. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.
    ConnectorNo auth
  • Free. Invest USDC into your vault from $1 (USDC 6 decimals: "1000000" = $1). Easiest: set usePermit=true with owner, sign the returned typedData off-chain (free), then call again with permitDeadline + permitSignature to get ONE deposit transaction. Without a permit you get two transactions (approve, then deposit). Returns an UNSIGNED transaction {to, data, value, chainId} on Base; nothing happens until you sign it with your own wallet and broadcast it. Liquid never holds keys or funds.
    ConnectorNo auth
  • Query raw Bitcoin transactions and optionally attach inputs and outputs inline. COMMON USER ASKS: - Recent Bitcoin transactions - Attach inputs and outputs WHEN TO USE: - You need raw Bitcoin transaction records. - You want the UTXO envelope without switching to separate input/output tools. DON'T USE: - You only need a quick wallet or network summary. EXAMPLES: - Recent Bitcoin transactions: {"network":"bitcoin-mainnet","timeframe":"1h","limit":20} - Attach inputs and outputs: {"network":"bitcoin-mainnet","timeframe":"1h","include_inputs":true,"include_outputs":true,"limit":10}
    ConnectorNo auth
  • Explains exactly how to claim work and what happens after. Claiming is free. Returns instructions, never performs the claim, because claiming requires the worker's own wallet signature.
    ConnectorNo auth