Skip to main content
Glama
131,602 tools. Last updated 2026-05-11 14:29

"How to transfer money using PayPal" matching MCP tools:

  • extract_facts_from_sessions

    VaultCrux Memory Core

    Scan the tenant's seeded sessions with rule-based extractors (money, counts, dates, project-role, acquire, version-chain) and emit structured facts to the projection stream so they become queryable via enumerate_memory_facts. Use when enumerate_memory_facts returns insufficient rows for aggregation, version-chain, or money questions and you suspect the fact exists but was under-predicated at ingest. Idempotent — safe to re-run (duplicate fact_hashes skipped unless overwrite_existing=true). Profile 'comprehensive' runs all rule families; narrower profiles ('money', 'counts', 'dates', 'version_chains') target a single family. Returns facts_added + rules_matched + receipt_id. Gated by FACT_EXTRACTION_MODE on the server.
    Connector

  • mark_job_paid

    Human Pages

    Record payment for an ACCEPTED job. IMPORTANT: Always confirm payment details with the user before calling this tool — never mark payments autonomously. Job must be in ACCEPTED status (use get_job_status to check). Crypto payments (usdc, eth, sol): provide tx hash + network → verified on-chain instantly, job moves to PAID. Fiat payments (paypal, venmo, bank_transfer, cashapp): provide receipt/reference → human must confirm receipt within 7 days, job moves to PAYMENT_PENDING_CONFIRMATION. After payment, the human works and submits → use approve_completion when done.
    Connector

  • get_human_profile

    Human Pages

    Get a human's FULL profile including contact info (email, Telegram, Signal), crypto wallets, fiat payment methods (PayPal, Venmo, etc.), and social links. Requires agent_key from register_agent. Rate limited: PRO = 50/day. Alternative: $0.05 via x402. Use this before create_job_offer to see how to pay the human. The human_id comes from search_humans results.
    Connector

  • get_transfer_code

    instadomain

    Get the EPP/transfer authorization code for a completed domain purchase. Args: order_id: The order ID of a completed domain purchase.
    Connector

  • get_about

    Follow On Tours

    Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Paypal

    PayPal MCP Pack — read-only access to PayPal transactions, orders, invoices, and disputes.

  • money

    Personal finance assistant — track transactions, budgets, net worth via Plaid

  • bulk_transfer_ens_names

    Name Whisper — ENS Intelligence Layer

    Transfer multiple ENS names in a single transaction via Multicall3 — bulk send. Much cheaper and faster than transferring names one at a time. Supports up to 20 names per batch. Automatically detects whether each name is wrapped (NameWrapper/ERC-1155) or unwrapped (BaseRegistrar/ERC-721) and builds the correct transfer call for each. All names can go to the same recipient or to different recipients — specify a toAddress per name. Requirements: - The fromAddress must currently own ALL names in the batch - All addresses must be valid Ethereum addresses - Names must be registered (not expired) WARNING: This transfers FULL ownership of every name. Recipients gain complete control. Resolver records (avatar, addresses, etc.) are NOT affected by transfer — they stay on each name. After transfer, consider using bulk_set_records to update ETH address records on the transferred names.
    Connector

  • get_daily_brief

    OneQAZ Trading Intelligence

    Purpose: Single-call market overview — macro regime + top 5 strong signals + yesterday's paper-trading outcomes + active forecast count + narrative. Use this as the first call when answering "how is the market today?". When to call: morning briefings, "today/yesterday how was the market?" queries. Prerequisites: none. Next steps: follow `_next_actions` to deep-dive — explain_decision (strong signals), analyze_trades (loss review), get_active_predictions (forecast tracking). Caveats: 24-hour window. Paper-trading data only (NOT real money). Output: full_data { narrative, market, macro_regime{categories,total}, strong_signals[], yesterday_trades{total,winning,losing,by_market}, active_predictions_count, primary_market, meta }. Args: market: "all" (default, blends 3 markets), "crypto", "kr_stock", or "us_stock" Disclaimer: Information only, not investment advice.
    Connector

  • knowledge_query

    DialogBrain

    Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.
    Connector

  • explain_queueing_theory

    QueueSim

    Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' question rather than asking for a number.
    Connector

  • transferOwnership

    ens-mcp

    Call transferOwnership(newOwner: string). Restricted: requires onlyOwner — only the owner address can call this. Transfers ownership to a new address. The new owner must call acceptOwnership() to complete the transfer (two-step pattern). No return value.
    Connector

  • unlock_domain

    instadomain

    Remove the registrar transfer lock from a completed domain purchase. Args: order_id: The order ID of a completed domain purchase.
    Connector

  • token_transfers

    Nansen

    Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - **Time**: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format) - **From Label**: Source address label (from_address_label: sender of tokens) - **To Label**: Destination address label (to_address_label: receiver of tokens) - **From Address**: Raw source address (from_address: hex address) - **To Address**: Raw destination address (to_address: hex address) - **Amount**: Quantity of tokens transferred (transfer_amount: numeric) - **Value USD**: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted) - **Type**: Transfer category (transaction_type: DEX, CEX, transfer, etc.) - **Tx Hash**: Blockchain transaction hash for verification (transaction_hash) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount, valueUsd Examples: # Basic request (most recent transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "order_by": "timestamp", "order_by_direction": "desc" } ``` # Smart money only filter (largest transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "transferOriginCategories": ["all_transfers"], "onlySmartTradersAndFunds": true, "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by DEX only with minimum transfer value (USD) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "transferOriginCategories": ["dex"], "transferValueUsd": {"from": 1000} } ``` # Filter transfers sent FROM a specific wallet ``` { "chain": "base", "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "dateRange": {"from": "2025-03-12", "to": "2025-03-12"}, "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "order_by": "timestamp", "order_by_direction": "desc" } ``` **Available Filters:** Address Filters: - **fromAddress** (str or list[str], optional): Filter by sender address(es) Example: "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72" Example: ["0xaddr1", "0xaddr2"] - **toAddress** (str or list[str], optional): Filter by recipient address(es) Use fromAddress/toAddress when looking for a specific wallet's transfers. Transfer Origin Categories: - **transferOriginCategories** (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples: - ['dex'] - only DEX transfers - ['cex'] - only CEX transfers - ['dex', 'cex'] - both DEX and CEX - ['non_exchange_transfers'] - only non-exchange transfers - ['all_transfers'] - all types (default) Smart Money Filter: - **onlySmartTradersAndFunds** (bool): Only show smart money transfers (default: false) When true, filters to show **only** transfers involving profitable addresses Numeric Range Filter: - **transferValueUsd** (object, optional): Filter by USD value of transfer Format: {"from": X, "to": Y} or {"from": X} or {"to": Y} - Specify only `from` for minimum bound (no maximum) - Specify only `to` for maximum bound (no minimum) - Specify both for a bounded range Example: {"from": 1000} - only transfers worth at least $1,000 USD Example: {"to": 50000} - only transfers up to $50,000 USD Example: {"from": 1000, "to": 50000} - transfers between $1,000 and $50,000 USD Note: This filters by the USD value of the transfer at time of transaction Notes: - Use fromAddress/toAddress to find transfers for a specific wallet - Use transferOriginCategories to control which transfer origins are included - Smart Money filter shows **only** transfers involving profitable addresses (definition of *Smart Money*) - transferValueUsd filters by USD value at time of transaction
    Connector

  • explain_guard_product

    CurrencyGuard Guard Pricing

    Explain the Guard product using CurrencyGuard's approved product and FAQ content. Use this for any question about what the Guard is, how it works, who it is for, how it compares to forwards or options, and for any legal, regulatory, accounting, or eligibility question. Do not answer those questions from memory — always call this tool.
    Connector

  • get_about

    cricket-travel

    Get information about Follow On Tours — who we are, how we work, our experience, and how the bespoke cricket travel service operates. Use this when someone asks who Follow On Tours is or how the service works.
    Connector

  • queryMetrics

    mcp

    # Instructions 1. Query OpenTelemetry metrics stored in Axiom using MPL (Metrics Processing Language). NOT APL. 2. The query targets a metrics dataset (kind "otel-metrics-v1"). 3. Use listMetrics() to discover available metric names in a dataset before querying. 4. Use listMetricTags() and getMetricTagValues() to discover filtering dimensions. 5. ALWAYS restrict the time range to the smallest possible range that meets your needs. 6. NEVER guess metric names or tag values. Always discover them first. # MPL Query Syntax A query has three parts: source, filtering, and transformation. Filters must appear before transformations. ## Source ``` <dataset>:<metric> ``` Backtick-escape identifiers containing special characters: ``my-dataset``:``http.server.duration`` ## Filtering (where) Chain filters with `|`. Use `where` (not `filter`, which is deprecated). ``` | where <tag> <op> <value> ``` Operators: ==, !=, >, <, >=, <= Values: "string", 42, 42.0, true, /regexp/ Combine with: and, or, not, parentheses ## Transformations ### Aggregation (align) — aggregate data over time windows ``` | align to <interval> using <function> ``` Functions: avg, sum, min, max, count, last Intervals: 5m, 1h, 1d, etc. ### Grouping (group) — group series by tags ``` | group by <tag1>, <tag2> using <function> ``` Functions: avg, sum, min, max, count Without `by`: combines all series: `| group using sum` ### Mapping (map) — transform values in place ``` | map rate // per-second rate of change | map increase // increase between datapoints | map + 5 // arithmetic: +, -, *, / | map abs // absolute value | map fill::prev // fill gaps with previous value | map fill::const(0) // fill gaps with constant | map filter::lt(0.4) // remove datapoints >= 0.4 | map filter::gt(100) // remove datapoints <= 100 | map is::gte(0.5) // set to 1.0 if >= 0.5, else 0.0 ``` ### Computation (compute) — combine two metrics ``` ( `dataset`:`errors_total` | group using sum, `dataset`:`requests_total` | group using sum; ) | compute error_rate using / ``` Functions: +, -, *, /, min, max, avg ### Bucketing (bucket) — for histograms ``` | bucket by method, path to 5m using histogram(count, 0.5, 0.9, 0.99) | bucket by method to 5m using interpolate_delta_histogram(0.90, 0.99) | bucket by method to 5m using interpolate_cumulative_histogram(rate, 0.90, 0.99) ``` ### Prometheus compatibility ``` | align to 5m using prom::rate // Prometheus-style rate ``` ## Identifiers Use backticks for names with special characters: ``my-dataset``, ``service.name``, ``http.request.duration`` # Examples Basic query: `my-metrics`:`http.server.duration` | align to 5m using avg Filtered: `my-metrics`:`http.server.duration` | where `service.name` == "frontend" | align to 5m using avg Grouped: `my-metrics`:`http.server.duration` | align to 5m using avg | group by endpoint using sum Rate: `my-metrics`:`http.requests.total` | align to 5m using prom::rate | group by method, path, code using sum Error rate (compute): ( `my-metrics`:`http.requests.total` | where code >= 400 | group by method, path using sum, `my-metrics`:`http.requests.total` | group by method, path using sum; ) | compute error_rate using / | align to 5m using avg SLI (error budget): ( `my-metrics`:`http.requests.total` | where code >= 500 | align to 1h using prom::rate | group using sum, `my-metrics`:`http.requests.total` | align to 1h using prom::rate | group using sum; ) | compute error_rate using / | map is::lt(0.2) | align to 7d using avg Histogram percentiles: `my-metrics`:`http.request.duration.seconds.bucket` | bucket by method, path to 5m using interpolate_delta_histogram(0.90, 0.99) Fill gaps: `my-metrics`:`cpu.usage` | map fill::prev | align to 1m using avg
    Connector

  • evaluate_service

    Agentic Platform

    Evaluate any MCP service for trustworthiness before spending money on it. Connects to the target server, checks reachability, governance declarations, tool definition quality, and audit endpoints. Returns a trust score from 0 to 100 with a recommendation: PROCEED, PROCEED WITH CAUTION, HIGH RISK, or DO NOT TRANSACT. No API key needed.
    Connector

  • token_transfers

    Nansen

    Get 25 token transfers (per page) for a specific token based on the sort order. Default is most recent transfers first. **NOTE:** This tool does not support native tokens (so11111111111111111111111111111111111111112, 0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee). Columns returned: - **Time**: Timestamp when the transfer occurred (block_timestamp: ISO 8601 format) - **From Label**: Source address label (from_address_label: sender of tokens) - **To Label**: Destination address label (to_address_label: receiver of tokens) - **From Address**: Raw source address (from_address: hex address) - **To Address**: Raw destination address (to_address: hex address) - **Amount**: Quantity of tokens transferred (transfer_amount: numeric) - **Value USD**: USD value of the transfer at time of transaction (transfer_value_usd: currency formatted) - **Type**: Transfer category (transaction_type: DEX, CEX, transfer, etc.) - **Tx Hash**: Blockchain transaction hash for verification (transaction_hash) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, amount, valueUsd Examples: # Basic request (most recent transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "order_by": "timestamp", "order_by_direction": "desc" } ``` # Smart money only filter (largest transfers first) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "transferOriginCategories": ["all_transfers"], "onlySmartTradersAndFunds": true, "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by DEX only with minimum transfer value (USD) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"}, "transferOriginCategories": ["dex"], "transferValueUsd": {"from": 1000} } ``` # Filter transfers sent FROM a specific wallet ``` { "chain": "base", "tokenAddress": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913", "dateRange": {"from": "2025-03-12", "to": "2025-03-12"}, "fromAddress": "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72", "order_by": "timestamp", "order_by_direction": "desc" } ``` **Available Filters:** Address Filters: - **fromAddress** (str or list[str], optional): Filter by sender address(es) Example: "0x2b060b9c89B8aD04e5E1fD40F1f327e41DD32c72" Example: ["0xaddr1", "0xaddr2"] - **toAddress** (str or list[str], optional): Filter by recipient address(es) Use fromAddress/toAddress when looking for a specific wallet's transfers. Transfer Origin Categories: - **transferOriginCategories** (list[str]): List of transfer types to include Possible values: ['dex', 'cex', 'non_exchange_transfers', 'all_transfers'] Default: ['all_transfers'] Examples: - ['dex'] - only DEX transfers - ['cex'] - only CEX transfers - ['dex', 'cex'] - both DEX and CEX - ['non_exchange_transfers'] - only non-exchange transfers - ['all_transfers'] - all types (default) Smart Money Filter: - **onlySmartTradersAndFunds** (bool): Only show smart money transfers (default: false) When true, filters to show **only** transfers involving profitable addresses Numeric Range Filter: - **transferValueUsd** (object, optional): Filter by USD value of transfer Format: {"from": X, "to": Y} or {"from": X} or {"to": Y} - Specify only `from` for minimum bound (no maximum) - Specify only `to` for maximum bound (no minimum) - Specify both for a bounded range Example: {"from": 1000} - only transfers worth at least $1,000 USD Example: {"to": 50000} - only transfers up to $50,000 USD Example: {"from": 1000, "to": 50000} - transfers between $1,000 and $50,000 USD Note: This filters by the USD value of the transfer at time of transaction Notes: - Use fromAddress/toAddress to find transfers for a specific wallet - Use transferOriginCategories to control which transfer origins are included - Smart Money filter shows **only** transfers involving profitable addresses (definition of *Smart Money*) - transferValueUsd filters by USD value at time of transaction
    Connector

  • get_slidev_guide

    Slidev MCP

    Get the Slidev syntax guide: how to write slides in markdown. Returns the official Slidev syntax reference (frontmatter, slide separators, speaker notes, layouts, code blocks) plus built-in layout documentation and an example deck. Call this once to learn how to write Slidev presentations.
    Connector