Skip to main content
Glama
132,185 tools. Last updated 2026-05-11 19:23

"Trade-In Value Estimator for Canada" matching MCP tools:

  • Get DEX trades for a specific token. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") **NOTE:** In onchain_tokens mode, only ETH is supported among native tokens. For other native tokens (SOL, BTC, BNB, etc.), use perps mode instead. Args: request: TokenDexTradesRequest containing parameters, pagination settings, and optional sorting Returns: DEX trading activity as markdown. Returns empty string if no trades found. **Common Columns (all modes):** - **Time**: Timestamp when the trade occurred (datetime: YYYY-MM-DD HH:MM:SS) - **Token**: Symbol of the token/perpetual contract - **Price USD**: Price per token in USD at time of trade (currency formatted) - **Value USD**: Total USD value of the trade/position change (currency formatted) - **Trader**: Nansen label or name of the trading address - **Tx Hash**: Blockchain transaction hash for verification **onchain_tokens mode:** - **Action**: Trade direction - BUY or SELL from perspective of the token - **Token Amount**: Quantity of the target token traded (numeric) - **Traded Amount**: Quantity of the other token in the swap (numeric) - **Traded Token**: Symbol of the token traded against (e.g., WETH, USDC) **perps mode:** - **Side**: Position direction - Long or Short - **Action**: Order action - Add, Reduce, Open, Close - **Size**: Quantity of the perpetual contract (numeric) Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, valueUsd, amount, priceUsd Examples: # On-chain tokens (default mode) ``` { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "24H_AGO", "to": "NOW"} } ``` # Hyperliquid perpetual futures ``` { "mode": "perps", "tokenAddress": "PENGU", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "action": "Open", "side": "Long" } ``` # Find biggest trades by USD value (whale watching) ``` { "mode": "onchain_tokens", "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "7D_AGO", "to": "NOW"}, "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Find who bought the dip vs who bought the top (price analysis) ``` { "chain": "ethereum", "tokenAddress": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "dateRange": {"from": "30D_AGO", "to": "NOW"}, "order_by": "priceUsd", "order_by_direction": "asc" } ```
    Connector
  • Get recent Hyperliquid perpetual futures trades from Smart Traders and Funds across all tokens. This tool provides granular smart trader and funds activity. For a big picture view of smart traders and funds activity across all tokens, use token_discovery_screener with traderType="sm" filter. **Note:** This endpoint is Hyperliquid-only (perpetual futures data). It returns recent trades only (no date filtering available). Columns returned: - **Time**: Timestamp when the trade occurred (datetime: YYYY-MM-DD HH:MM:SS) - **Side**: Position direction - Long or Short - **Action**: Order action - Add, Reduce, Open, Close - **Token**: Symbol of the perpetual contract - **Size**: Quantity of the perpetual contract (numeric) - **Price USD**: Price per token at time of trade (price formatted) - **Value USD**: Total USD value of the trade (currency formatted) - **Trader**: Nansen label of the trading address - **Tx Hash**: Blockchain transaction hash for verification Sorting Options (all fields support "asc"/"desc"): Available for sorting: timestamp, valueUsd, amount, priceUsd Examples: # Get recent smart money perp trades (sorted by value) ``` { "order_by": "valueUsd", "order_by_direction": "desc" } ``` # Filter by action and side ``` { "action": "Open", "side": "Long", "includeSmartMoneyLabels": ["Fund", "All Time Smart Trader"] } ```
    Connector
  • Pre-flight credit estimator for a list of URLs. Returns counts + credit estimate. Free, no credits consumed. Call this before check_urls to show the user how many credits the batch will cost. Classifies each URL against three free gates: - tranco: URL's registrable domain is in the Tranco top 100K (trusted, treated as clean with score 0, no pipeline needed) - cached: URL's hostname is already in Unphurl's reputation cache (results available, no pipeline needed) - unknown: URL needs full pipeline analysis (costs 1 credit per URL) Returns counts for each gate plus total, credits_needed, credits_min, and credits_max. credits_min and credits_max are both equal to the unknown count in the current implementation. Maximum 500 URLs per call. Rate limit: 10 requests per minute. Does not follow redirects; classifies each URL as submitted. Typical agent flow: 1. Collect a list of URLs 2. Call estimate_urls to get the cost breakdown 3. Show the user the breakdown and ask for approval 4. On approval, call check_urls on the unknowns only
    Connector
  • Confirm a narrative lens and generate targeted CV edits with trade-offs (5 credits, takes 20-30s). Returns an array of section edits with before/after text, trade-off notes, and optionally clean + review PDF download URLs. This is step 3 (final step) of the positioning pipeline. Pass confirmed_lens from ceevee_analyze_positioning, and optionally positioning_snapshot, detected_lens_full, recruiter_inference, selected_opportunities from prior steps for richer edits. Use ceevee_explain_change to understand any specific edit.
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Census Trade MCP — US Census Bureau International Trade data

  • Trade Intel MCP — Compound tools that chain Comtrade, Census, Treasury,

  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Update the bonus entries value for a participant in a sweepstakes. This overwrites the current value. Use get_participant first to check current bonus entries. # update_bonus_entries ## When to use Update the bonus entries value for a participant in a sweepstakes. This overwrites the current value. Use get_participant first to check current bonus entries. ## Pre-calls required 1. fetch_sweepstakes if the user gave you a sweepstakes name instead of a token ## Parameters to validate before calling - sweepstakes_token (string, required) — The sweepstakes token (UUID format) - participant_token (string, required) — The participant token (UUID format) - bonus_entries (integer, required) — range: 0–1000000 — New bonus entries value (0-1000000). This overwrites the current value.
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Verify factual claims about current DeFi market conditions. Supports two modes: - Single claim: provide claim_type, value, operator (and protocol/chain/asset as needed). Returns one verification result. - Batch mode: provide a JSON-encoded array in 'claims'. Each element has the same fields (claim_type, value, operator, protocol, chain, asset). Returns all results in one response. If 'claims' is provided, single-claim parameters are ignored. Args: api_key: Your PreFlyte API key (required). claim_type: What you're checking. One of: "supply_rate" — current supply APY (%) "borrow_rate" — current borrow APY (%) "price" — current token price (USD) "gas" — current base fee (gwei) "utilization" — current pool utilization (%) value: The numeric value you believe to be true. operator: Comparison operator. One of: "above" — actual must be >= value "below" — actual must be <= value "around" — actual must be within 10% of value protocol: Required for supply_rate, borrow_rate, utilization. Use "aave-v3" or "compound-v3". chain: Chain name — "ethereum" or "arbitrum". Default "ethereum". asset: Required for supply_rate, borrow_rate, price, utilization. Use token symbol like "USDC", "WETH", etc. claims: JSON-encoded array of claim objects for batch verification. Each object contains: claim_type, value, operator, and optionally protocol, chain, asset. When provided, single-claim params are ignored. Returns: Single mode: Dictionary with status (TRUE/FALSE), actual_value, claimed_value, delta, delta_pct, data_timestamp, and summary. Batch mode: Dictionary with 'mode', 'results' array, 'summary' counts, and 'verified_at' timestamp. Examples: Single: verify_claim(api_key="...", claim_type="supply_rate", value=5.0, operator="above", protocol="aave-v3", asset="USDC") Batch: verify_claim(api_key="...", claims='[{"claim_type": "supply_rate", ...}, ...]')
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector
  • Ask a question in plain English and get an answer from the best available data source. Pipeworx picks the right tool, fills the arguments, and returns the result. No need to browse tools or learn schemas — just describe what you need. Examples: "What is the US trade deficit with China?", "Look up adverse events for ozempic", "Get Apple's latest 10-K filing".
    Connector