Skip to main content
Glama
343,369 tools. Last updated 2026-07-30 13:44

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

  • READ-ONLY wallet summary for a SOMA app user: their SOMA Coins balance plus a summary of coins expiring within the next 30 days. Requires a wallet token that only the human can generate inside the SOMA mobile app (Wallet tab → 'Share balance with your AI') — ask them for it; tokens expire after ~10 minutes. This tool can never claim, redeem, spend, or move coins (there are deliberately no claim/redeem tools over MCP). Returns { error: 'invalid_or_expired_token' } for a bad or stale token — ask the user to generate a fresh one in the app.
    Connector
  • 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.
    Connector
  • The user's wallet: every live card they hold, with IDs, last four digits, expiry, balance, and status. Start here to find available cards; if none are returned, call create_card to issue one. When the shared wallet is enabled, `wallet` lists every card across all connected apps and companies, each tagged with its source (kind personal/company, the minting app, and the company where applicable) — cards minted by another app or company are read-only from this session: get_card_details and close_card will not work on them.
    Connector
  • 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.
    Connector
  • The exact ready-to-sign tx that kills an approval — approval-advisor tells you WHAT to revoke; this builds the HOW: the ready-to-sign transaction (to + calldata) for approve(spender, 0) on a token, plus the live current allowance read from Base (flags unlimited, or 'already revoked'). Hand the result straight to a wallet or agent signer — the action half of approval hygiene. Required inputs: token, spender. 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.
    Connector
  • 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.
    Connector

Matching MCP Servers

  • -
    license
    -
    quality
    C
    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.
    Last updated

Matching MCP Connectors

  • MCP server for verifying EUDI/Talao wallet data via OIDC4VP (pull) for AI agents.

  • Multi-chain wallet MCP. 18 tools: balance, swap, bridge, stake, claim. Pay-per-call USDC (x402 v2).

  • One StonkBroker by id (1-4444): owner, its ERC-6551 wallet address and holdings, the stock it was seeded with, per-stock dividends received, activation tier, whether its wallet owns a Floor desk (floor.hasDesk), and its on-chain art. null means unknown, never zero.
    Connector
  • Request a one-time verification challenge to prove ownership of an XRPL wallet. The wallet owner must submit an AccountSet transaction on XRPL with a Memo containing the returned challenge string (as hex). No private key is ever sent — the on-chain tx itself is the proof, since only the key-holder can sign and broadcast from that address. After broadcasting the tx, call confirm_wallet_ownership() with the tx hash. Challenge expires in 30 minutes. Returns: wallet, challenge, memo_hex, expires_at, instructions.
    Connector
  • Creates a payment wallet. Payment wallets are a form of sub-wallet of which the sponsor controls access to the Secret,PIN and recovery keywords. A payment wallet cannot login to the portal and is therefore only accessible to the sponsor via the api or this mcp. In order for this wallet to exists, it needs to be created by a human KYCed wallet. Once created this wallet will be fully enabled to perform any transaction any other wallet is capable of. Including access to virtual bank accounts in Europe and the USA as a funding source. The wallet is automatically minted with a Solana Blockchain wallet. The sponsor would typically only need to save the wallet_fk and PIN of the new wallet in their storage in order to make use of it later. The secret is optional purely to maintain backward compatibility, if not provided the system will generate default values. We suggest you use the mobile and email of the sponsor where available, in order to get access to recovery methods. The human accepts all legal responsibility for this payment wallet. Process can take up to 30 seconds. @param secret: A secret, minimum 8 characters, must be unique system-wide. This is typically the username, but private. Suggestion: Generate 3 natural language words, concatenated, or prompt the human for 3 words. @param pin: The 5 digit PIN associated with the new wallet. Can be any random 5 numbers. @param email: The agents email address, if not available use a blank string. @param mobile: The human's mobile phone number, in e164 format, e.g. 27821234567 (no +). if not available use a blank string. @param currency_fk: The currency of the first account, use 7 (ZAR) for everyone else use 3 (USD) @param sponsor_wallet_fk: The sponsor's wallet_fk, this wallet_fk must be KYCed if not the new wallet will also not be KYCed @param sponsor_wallet_pin: The sponsor's 5-digit PIN @return: a json object
    Connector
  • Service health and current coverage: chains, wallet types, periods, limits and how many wallets are tracked per chain. Useful when a query returns nothing and it is unclear whether the data exists at all.
    Connector
  • Period statistics for ONE wallet: realized PnL, win rate, volume, trade counts, active tokens and win-rate distribution. The main tool for "how is this trader doing". blockchain: solana, bnb, base, eth or rh address: the wallet address period: 6h, 1d, 7d or 30d (default 1d). Longer periods return far more data and are trimmed harder; prefer the shortest period that answers it.
    Connector
  • [verify] Step 1 of wallet verification: get a fresh challenge for the user to sign. chain: "evm" or "solana". Pass agent_id (your marketplace identity) so the proof is bound to you. Present `challenge` to the user, have their wallet sign it (EVM personal_sign / Solana signMessage), then call verify_wallet_ownership with the returned `nonce` + signature. The challenge is single-use and expires (~10 min). Returns {challenge, nonce, expires_at}.
    Connector
  • Step 1 of wallet verification: get a fresh challenge for the user to sign. chain: "evm" or "solana". Pass agent_id (your marketplace identity) so the proof is bound to you. Present `challenge` to the user, have their wallet sign it (EVM personal_sign / Solana signMessage), then call verify_wallet_ownership with the returned `nonce` + signature. The challenge is single-use and expires (~10 min). Returns {challenge, nonce, expires_at}.
    Connector
  • Build a NON-CUSTODIAL Solana DEX swap via Jupiter: returns an UNSIGNED base64 transaction — sign with YOUR OWN wallet and send to any Solana RPC. Server never touches funds. 0.3% on-chain routing fee.
    Connector
  • Return the unsigned payload for a USER-signed wallet to complete: the tx object and, for Permit2 settlement, the EIP-712 typed data plus the byte offset where the wallet layer splices the 65-byte signature. This server never signs — it only shapes what a wallet needs to sign.
    Connector
  • Browse agents and humans offering skills on the AgentTrust marketplace. Skill listings are published by workers (agents or humans) who want to be found and hired directly — no bidding required. Each listing shows the poster's XRPL wallet address so a buyer can skip the job board entirely and go straight to creating an escrow. Workflow to direct-hire a skill provider: 1. list_marketplace_skills() — find a suitable provider (filter by category/rate) 2. direct_hire(skill_id) — get the worker's wallet address + escrow instructions 3. create_escrow_vault(worker_address=..., amount_xrp=...) — lock payment Returns: skills: List with id, title, description, category, rate, rate_xrp, poster (wallet address), poster_name, tags, expires_at, is_demo. total, real_skills, demo_skills.
    Connector
  • [free] What this connector is and how to pay for the tools it fronts: catalog size, the free compute tier and its limits, the payment rails accepted, and the machine-readable discovery URLs. Call this first if you need to know whether a wallet is required.
    Connector
  • 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.
    Connector
  • Get all ENS names owned by a wallet address. Returns each name with label, tags, expiry, registration date, and active listing/offer prices. Useful for portfolio analysis and wallet profiling. If you are authenticated via ERC-8128 and omit the wallet parameter, your own wallet is used automatically.
    Connector
  • Create an anonymous participation session for a PoolParty channel. Returns a sessionToken for use with submit_media_block. Requires API key with submit:block scope. Session allows up to 3 anonymous submissions. Wallet is required for reward eligibility and reward claims, not for submission.
    Connector