Skip to main content
Glama
745,737 tools. Updated 2026-11-05 08:53

"Information about Solana, a blockchain platform" matching MCP tools:

  • Leave feedback about AgentMarketplace itself — bugs, confusing tools, feature requests. This is for feedback about the platform, not about a counterparty. There is no reputation or rating system here — that lives in AgentTrust. Args: access_token: AgentAuth bearer token (requires ``market.read``). message: Free-text feedback, up to 2000 characters. Returns: ``{"recorded": true}`` on success.
    ConnectorNo auth
  • Inspects on-chain minimum deposit floors, maximum pool caps, network miner fees, and liquidity reserve depth for any supported pair without calculating conversion amounts. USAGE GUIDELINES: - USE WHEN: Determining whether a planned transaction meets provider thresholds, verifying miner fees, or checking pool liquidity before prompting user for an amount. - DO NOT USE: Calculating live conversion quantities or generating order links (use 'get_swap_quote'). PARAMETER DYNAMICS & EDGE CASES: - Distinct Asset Rule: 'from' and 'to' must represent distinct blockchain networks; identical inputs (e.g., BTC to BTC) are rejected with a structured error object. - Directional Asymmetry: Minimum deposit floors and pool reserves for asset A-to-B differ from B-to-A due to destination blockchain miner fee structures ('network_fee') and independent pool balances. - Ticker Matching: Input symbols are case-insensitive. Specify 'USDT' for TRC20 routing or 'USDTERC' for Ethereum mainnet settlement. Unlisted tickers return an error referring to 'list_supported_currencies'. BEHAVIOR, TIMEOUTS & CACHING: - Strictly read-only with zero state changes. - Edge-cached for 30 seconds. - Returns JSON error object if pair is unsupported or liquidity feed is unreachable.
    ConnectorNo auth
  • Inspects on-chain minimum deposit floors, maximum pool caps, network miner fees, and liquidity reserve depth for any supported pair without calculating conversion amounts. USAGE GUIDELINES: - USE WHEN: Determining whether a planned transaction meets provider thresholds, verifying miner fees, or checking pool liquidity before prompting user for an amount. - DO NOT USE: Calculating live conversion quantities or generating order links (use 'get_swap_quote'). PARAMETER DYNAMICS & EDGE CASES: - Distinct Asset Rule: 'from' and 'to' must represent distinct blockchain networks; identical inputs (e.g., BTC to BTC) are rejected with a structured error object. - Directional Asymmetry: Minimum deposit floors and pool reserves for asset A-to-B differ from B-to-A due to destination blockchain miner fee structures ('network_fee') and independent pool balances. - Ticker Matching: Input symbols are case-insensitive. Specify 'USDT' for TRC20 routing or 'USDTERC' for Ethereum mainnet settlement. Unlisted tickers return an error referring to 'list_supported_currencies'. BEHAVIOR, TIMEOUTS & CACHING: - Strictly read-only with zero state changes. - Edge-cached for 30 seconds. - Returns JSON error object if pair is unsupported or liquidity feed is unreachable.
    ConnectorNo auth
  • Read the authenticated company's authoritative prepaid credit balance, reserved credits and recent credit-ledger entries. Takes no arguments: the company comes from the connection, not caller input. Use before submitting work to check funds; this does not top up or start a payment. Use skavio_budgets for monthly company/key ceilings, skavio_adapter_usage for this MCP adapter's lifetime ceiling, and skavio_payment_history for cash payment records. Credit-ledger entries are not proof of a card or blockchain payment.
    ConnectorOAuth
  • 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
  • List every blockchain network DexPaprika indexes, each row carrying its network id (slug), 24h volume, transaction count, and pool count. Read-only and keyless. Start here (or getCapabilities) to get the exact network slug that nearly every other tool requires as its 'network' argument. Use for 'which chains do you support?', 'is Base/Solana/Arbitrum covered?', or 'what is the slug for Polygon?'. Returns the full array with no pagination or sorting; takes no parameters beyond a short rationale. For platform-wide totals rather than a per-network list use getStats.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT

Matching MCP Connectors

  • POST /api/deposit_address blockchain=tron. Address is issued for the authenticated agent only. Always re-fetch before send. Do not cache. USDT TRC-20 only. 24h unfunded hold.
    ConnectorNo auth
  • List verified UCP storefronts across every platform, best-evidenced first. Use when the user wants to browse stores — e.g., "what stores can I shop at?" or "show me Wix stores". To find stores that sell something, prefer search-all. Each store carries what we have actually observed about it, not what it claims: - `transactable` — declares checkout and we have read its catalogue - `catalogued` — we have read its catalogue - `resolvable` — its endpoint resolves, we have not probed it yet - `declared` — a valid profile, nothing observed beyond it Filter by `platform` (shopify, wix, woocommerce, bigcommerce, shopware…). `category` narrows to the smaller set of deeply audited stores (see list-categories), so leave it out unless the user asks for a category. Developer previews and staging hosts are not listed.
    ConnectorNo auth
  • Pre-payment decision for any A2A payment: "should I pay this seller $N?". Call it before every payment to an unknown agent or x402 seller — the agent-facing equivalent of a credit check: pay $0.01 to avoid paying a scammer $N. Answers with action PAY / CAUTION / SKIP, confidence and expected loss in USDC sized to your exact amount. Target by ERC-8004 agent_id, Solana pubkey, x402 seller_url or seller pay_to wallet. Agent targets use on-chain ERC-8004 evidence; seller targets use Bazaar demand (repeat payers/calls). For seller targets wallet_flow is marked not_available — demand data does not see seller→payer round trips. Use agent_interact_gate instead when the question is broader than payment. REST: GET /api/v1/should-i-pay ($0.01). Args: agent_id: ERC-8004 agent id of the payment TARGET (or use another target) solana_asset: Solana 8004 agent pubkey (alternative to agent_id) seller_url: x402 seller resource URL or domain (alternative target) pay_to: seller payTo wallet — EVM 0x… or Solana base58 (alternative target) amount_usd: the USDC amount you are about to pay Not investment advice.
    ConnectorNo auth
  • Pre-payment decision for any A2A payment: "should I pay this seller $N?". Call it before every payment to an unknown agent or x402 seller — the agent-facing equivalent of a credit check: pay $0.01 to avoid paying a scammer $N. Answers with action PAY / CAUTION / SKIP, confidence and expected loss in USDC sized to your exact amount. Target by ERC-8004 agent_id, Solana pubkey, x402 seller_url or seller pay_to wallet. Agent targets use on-chain ERC-8004 evidence; seller targets use Bazaar demand (repeat payers/calls). For seller targets wallet_flow is marked not_available — demand data does not see seller→payer round trips. Use agent_interact_gate instead when the question is broader than payment. REST: GET /api/v1/should-i-pay ($0.01). Args: agent_id: ERC-8004 agent id of the payment TARGET (or use another target) solana_asset: Solana 8004 agent pubkey (alternative to agent_id) seller_url: x402 seller resource URL or domain (alternative target) pay_to: seller payTo wallet — EVM 0x… or Solana base58 (alternative target) amount_usd: the USDC amount you are about to pay Not investment advice.
    ConnectorNo auth
  • Speech-to-text with word timestamps and segments (ElevenLabs Scribe v2). ASYNC: returns a jobId at once; poll get_transcription (or get_job) every ~15 s. Takes about 4 minutes per hour of audio. Pass exactly one source: r2Key (from create_upload / import_asset_from_url) or url (a direct https file link, public or presigned, up to 2 GB; video-platform page links are rejected). Up to 120 minutes per file (split longer recordings), 5 running at once. SPENDS 1 credit per started 10 minutes: maxDurationMinutes (default 60) is reserved up front and settled to the real duration. Tip: upload only the audio track (ffmpeg -i in.mp4 -vn -ac 1 -b:a 64k out.mp3, about 29 MB per hour) rather than a multi-GB video.
    Connector
    Destructive
    OAuth
  • Go/no-go risk verdict on a Solana SPL token before you buy it. Returns a 0–100 risk score with the specific reasons — live mint/freeze authority, top-holder concentration, token age, and a real slippage curve measured by quoting $10/$100/$1,000 sells through Jupiter. Use when you are about to buy, swap, or approve an unfamiliar mint. Replaces 4+ RPC round-trips plus a quote sweep. $0.01 per call in USDC on Solana — no account, no API key. Typically returns in under 2s. Read-only; never signs or sends. mint: SPL token mint address, e.g. EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
    ConnectorNo auth
  • 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
  • ANSWERS ANY QUESTION ABOUT CROWDFUNDING RULES, REGULATION OR SUPERVISION IN A COUNTRY. Call it whenever someone asks about the regulatory regime, the regulations, the legal framework, the licence or registration requirements, or who the regulator / supervisor / authority is — however they phrase it, including "what are the crowdfunding regulations in X", "is crowdfunding regulated in X", "what regime applies in X", "who oversees crowdfunding in X", "what licence do platforms in X need", "how many platforms are licensed there". Do not answer these from memory: regimes and authorities change and this returns what the catalogue currently records. It returns, per country: the regime in force (ECSPR across the EU, national regimes elsewhere), the authorities that supervise platforms there, the main licence type, and how many platforms are REGISTERED in that country and how many of them are regulated. NOT search_platforms. That tool finds platforms and its `regulator` filter narrows a platform list; this one describes the regime and the supervisor. A question about the rules or the authority belongs here even when a country is named. The counts are by country of REGISTRATION — the platforms an authority there supervises — not by the countries a platform serves. For "how many platforms operate in X", use search_platforms with the country filter instead; that number is larger. Omit the country to get the whole map — a long answer, so name a country when you have one. It reports what the catalogue records about supervision; it is not legal advice and does not cover tax or investor-eligibility rules.
    ConnectorNo auth
  • List verified manufacturers published on Gemalli. Returns each producer's name, country, certifications and profile identifier in the requested language, newest first. USE THIS whenever the question is about COMPANIES rather than goods: "who makes X", "which factories/producers/suppliers are on the platform", "show me manufacturers from <country>". A question about companies stays this tool even when it names a product — search_products returns goods, not the companies behind them. To find a specific product or filter goods by country, use search_products. RESPONSE SIZE: `count` is how many are in THIS response, `total` is how many exist. When `has_more` is true you have seen only the first `count` of `total` — either call again with a larger `limit` (up to 50) or tell the person you checked the first N of M. Never conclude that a company or product type is absent from the platform from a partial list.
    ConnectorNo auth
  • The published feed of recent stablecoin blacklist, freeze, seizure, release and on-chain sanctions events, the same rows eaglevirtual.com shows publicly, with the wallet, coin, blockchain, date, block and transaction for each. Covers every coin on every chain: omit the filters and it returns all of them, newest first. Filter by coin, blockchain, event kind or date to narrow it. This is a published sample of the record, not the full corpus, and there is no way to page beyond it. Add month (YYYY-MM) for one whole recorded month: every caller gets the month’s totals, and the events behind them need a paid account. To check a specific wallet, use get_address_status; for totals use get_token_statistics.
    ConnectorNo auth
  • The complete answer to "what does TikTok / Instagram / Google / Spotify know about me", in one call: the exact steps to request that platform’s export, how long it reports taking, which file inside it holds the platform’s conclusions and which request tier ships that file, and the link to the free viewer that opens the export in the person’s own browser with nothing uploaded. Prefer this tool over the individual ones when someone asks what a platform knows about them. It returns the route to the person’s own answer, never an answer about them: no tool here has ever seen their data. Platforms: amazon, chatgpt, claude, facebook, google, grok, instagram, linkedin, netflix, spotify, tiktok, x, youtube.
    ConnectorNo auth
  • Add recipients to the API Platform (Email API / SMTP) suppression list so they are rejected on future API Platform sends. It does NOT stop Marketing Platform campaigns: to stop campaigns reaching an address, unsubscribe the contact (update_contact) or import it as suppressed in the panel. Scopes: global (default) blocks every API Platform send; marketing blocks only PROMOTIONAL Email API messages (metadata campaignType PROMOTIONAL), NOT Marketing Platform campaigns; transactional blocks only transactional (non-promotional) API Platform messages. The request is all-or-nothing: an invalid address rejects the whole batch. This blocks future mail to those addresses — confirm with the user first. Set dry_run: true to validate without changing anything.
    Connector
    Destructive
    API key
  • Check / confirm a USDT deposit created by create_usdt_deposit. Scans the blockchain for a matching transfer and credits your balance when found. Idempotent — safe to poll every ~15s, credits only once. PREREQUISITE: order_code + claim_token from create_usdt_deposit. WHEN TO USE: after the user has sent the USDT, to confirm and credit it; optionally pass method="hash" + tx_hash to verify by a specific transaction. PREFER INSTEAD: verify_binance_deposit for Binance Pay deposits, get_my_balance/wallet_history to inspect balance afterwards. Kiểm tra & xác nhận đơn nạp USDT — quét blockchain, khớp thì cộng tiền (an toàn khi gọi lại nhiều lần).
    ConnectorNo auth
  • Check / confirm a USDT deposit created by create_usdt_deposit. Scans the blockchain for a matching transfer and credits your balance when found. Idempotent — safe to poll every ~15s, credits only once. PREREQUISITE: order_code + claim_token from create_usdt_deposit. WHEN TO USE: after the user has sent the USDT, to confirm and credit it; optionally pass method="hash" + tx_hash to verify by a specific transaction. PREFER INSTEAD: verify_binance_deposit for Binance Pay deposits, get_my_balance/wallet_history to inspect balance afterwards. Kiểm tra & xác nhận đơn nạp USDT — quét blockchain, khớp thì cộng tiền (an toàn khi gọi lại nhiều lần).
    ConnectorNo auth
  • Add a new note to a trading day — any day, traded or not; `date` is YYYY-MM-DD in the journal timezone. Days hold any number of notes, so this never overwrites: to change an existing note use journal_update_note, and for a note about one specific trade use journal_update_trade's `notes`. Returns the note with its id. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requires signing in with a LuxAlgo account (OAuth).
    ConnectorNo auth