Skip to main content
Glama
189,980 tools. Last updated 2026-06-10 18:06

"Polygon" matching MCP tools:

  • Search 2.4B+ GBIF occurrence records with Darwin Core filters. Use taxonKey from gbif_match_species for reliable results — it resolves synonyms automatically. Accepts country (ISO 3166-1 alpha-2), bounding box (decimalLatitude/decimalLongitude ranges), WKT polygon geometry, year range, month, basis of record, and coordinate filter. Pagination is capped at approximately offset+limit=100,000 — use gbif_occurrence_facets for aggregate counts across large result sets.
    Connector
  • Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
    Connector
  • Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.
    Connector
  • Produce a Due Diligence Statement per Regulation (EU) 2023/1115 for one or more plots. Each plot carries operator-supplied geometry (GeoJSON Polygon for >4 ha, Point for ≤4 ha non-cattle per Article 2(28)), country of production (ISO3), Combined Nomenclature code (HS-6+), and quantity in kg. The endpoint applies the regulation's 10 % canopy / 0.5 ha / 5 m height forest definition (Article 2(4)) using the EU Commission's expected JRC GFC2020 V3 baseline plus Hansen GFC v1.12 loss-year confirmation; Sims et al. 2025 driver attribution and RADD SAR fallback layer on when those connectors are wired (Absence today). The response is an Annex II-shaped envelope with per-plot verdict (pass/fail/not_in_scope/indeterminate/below_mmu), failing-cell fraction, and signed fact CIDs for every per-cell verdict — operators quote them in the company's Article 12 record. Article 9(1)(b) legality (land tenure, FPIC, country-of-origin laws) is structurally out of EO scope; the response carries an explicit `legality_disclaimer` for that reason. When to use: Call when a commodity supplier or EU importer needs to evidence due diligence under Regulation (EU) 2023/1115. Use the plot-level signed receipts as evidence inside the operator's company record; pair with a partner legality module before submitting the final DDS to the EU Information System (TRACES NT). For a single plot, pass one entry in `plots`. For batch supply-chain audits, pass up to a few dozen plots in one call — the endpoint fans out per plot. Surface the failing-cell fraction, the chosen forest baseline, and the legality disclaimer in the user-facing response so the operator understands what the engine claims (and does not).
    Connector
  • Find x402 / MCP services matching an intent or filter set. Two usage modes (agents pick whichever fits): A. Natural-language: `search(intent="fetch tweets for @user")` B. Pure browse: `search(has_mcp=True, category="defi", top_k=10)` At least one of `intent`, `category`, `chain`, `has_mcp`, `min_confidence` must be supplied — otherwise the call is rejected (we won't dump 2300+ rows). Results are ranked by: (health=ok AND tx_30d>0) → health=ok → has-quality-signal → confidence → tx_30d → recency. So the highest-quality real-traffic services appear first. Each item includes (when available): - confidence : 0.0–1.0 x402scan quality score. - tx_30d : 30-day x402 payment count (proxy for real usage). - match_snippet : FTS snippet showing where `intent` hit ([[token]]). - match_reason : list[str] of human-readable ranking signals. - mcp_url : populated when the service exposes an MCP endpoint (you can call it directly via streamable-http). Agents should prefer items with non-null confidence and tx_30d > 0 unless the user explicitly wants experimental endpoints. Args: intent: What the agent wants to do (English or Chinese). Optional when at least one structured filter is set. Synonym expansion covers twitter↔X↔推特, whale↔巨鲸, price↔价格 etc. top_k: Max services to return (default 5, hard cap 25). max_price_usd: Upper bound on per-call price in USD. category: Filter (see `list_categories`). chain: "base", "polygon", "solana", "arbitrum", ... min_confidence: Minimum confidence (0.0–1.0). 0.8+ keeps only services x402scan rates as high-quality. has_mcp: When true, return only services with a callable MCP endpoint. Use this when the agent wants to chain another MCP server rather than perform raw HTTP+x402.
    Connector
  • Get comprehensive token screening data across multiple blockchain networks with advanced filtering. A maximum of 25 results are returned out of 1000s of tokens. Use the sorting and filtering options to narrow down the results. A maximum of 5 chains can be specified per request (excess chains are automatically trimmed). This tool helps with token discovery and finding trending tokens by combining different metrics: volume, liquidity, market cap, smart money activity, and token age. **IMPORTANT - Hyperliquid Special Case:** - Hyperliquid chain queries perpetual futures (perps), not spot tokens - When hyperliquid is mixed with other chains, two sections of up to 25 results each are returned - one for spot tokens and one for perps. - For perps, only these filters are supported: volume, buyVolume, sellVolume, openInterest, netflow, nofTraders, traderType - Additional orderBy fields for perps: openInterest, funding - Unsupported filters/orderBy will fallback to defaults INPUT EXAMPLES: # Find tokens which are going up in price. # Added some liquidity filter to remove spam and low quality tokens. ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "liquidity": {"from": 100000}, "nofTraders": {"from": 10}, "orderBy": "price_change", "orderByDirection": "desc" } ``` # Find top stablecoins by market cap ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["Stablecoin"], "orderBy": "market_cap_usd", "orderByDirection": "desc" } ``` # Find AI memecoins with high trading activity { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["AI Meme"], "liquidity": {"from": 100000}, "volume": {"from": 1000000} } # Find DeFi lending tokens { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "sectors": ["DeFi Lending (Money Markets)"], "netflow": {"from": 1000000} } # Find tokens which have a lot of buying activity (high nofBuyers and buyVolume) # Note that we added some filters to remove spam and low quality tokens. We added liquidity filter so that we only surface tokens which we can buy or sell. # We sort by `netflow` descending to get tokens with the most net buying activity. ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "liquidity": {"from": 100000}, "buyVolume": {"from": 1000000}, "marketCapUsd": {"from": 1000000}, "nofBuyers": {"from": 10}, "orderBy": "netflow", "orderByDirection": "desc" } ``` # Find Hyperliquid perps with high open interest and positive net flow ``` { "chains": ["hyperliquid"], "timeframe": "7d", "openInterest": {"from": 100000}, "volume": {"from": 1000000}, "netflow": {"from": 0}, "nofTraders": {"from": 10}, "orderBy": "netflow", "orderByDirection": "desc" } ``` WARNING: To avoid timeouts, it's recommended to: - Use 4 chains or less at a time (API tends to timeout with more chains) - Use shorter timeframes (e.g., 24h or 1h instead of 7d or 30d) Args: Returns: Comprehensive token metrics as markdown. Returns empty string if no tokens found. Columns returned: - **Token Address**: Token address (e.g., 0x1234567890123456789012345678901234567890) - **Symbol**: Token trading symbol (e.g., ETH, BTC, DOGE) - **Chain**: Blockchain network (ethereum, solana, polygon, etc.) - **Price USD**: Current token price in USD (currency formatted) - **Price Change**: Price change percentage over the date range (percentage, can be negative) - **Market Cap**: Current market capitalization (currency formatted) - **Fully Diluted Valuation (FDV)**: Market cap if all tokens were circulating (currency formatted) - **FDV/MC Ratio**: Ratio indicating how much supply is locked/vested (numeric, >1 means locked supply) - **USD Volume**: Total trading volume in USD (currency formatted) - **Buy USD Volume**: Total buy volume in USD (currency formatted) - **Sell USD Volume**: Total sell volume in USD (currency formatted) - **Net Flow USD**: Net flow (buys minus sells) in USD (currency formatted, can be negative) - **DEX Liquidity**: Available liquidity for trading (currency formatted) - **Inflow/FDV**: Inflow as percentage of FDV (percentage formatted) - **Outflow/FDV**: Outflow as percentage of FDV (percentage formatted) - **Token Age (Days)**: Days since token was first deployed - **Sectors**: List of token sectors/categories Hyperliquid perps columns (smart-money mode, when `onlySmartTradersAndFunds=true`): - **Net Position** (`LONG $X` / `SHORT $X` / `FLAT`): current net direction. Use this when answering long/short questions. - **Current Longs USD** / **Current Shorts USD**: gross notional on each side; sizing only, not direction. - **Net Position Change**: delta over the timeframe — can be positive while Net Position is still SHORT. Notes: - Positive Net Flow on spot tokens indicates more buying than selling - High FDV/MC Ratio suggests significant locked or vested tokens **Filtering Options** (filters parameter): - **Numeric Ranges**: volume, liquidity, marketCapUsd, netflow, tokenAgeDays, nofTraders, nofBuyers, nofSellers, nofBuys, nofSells, buyVolume, sellVolume, fdv, fdvMcRatio, inflowFdvRatio, outflowFdvRatio - **Categories**: sectors (e.g. ["AI", "Meme"]), includeSmartMoneyLabels - **Trader Type**: traderType (string: "all", "sm", "whale", "public_figure") - Use "sm" ONLY when user explicitly asks for "smart money". - Use "whale" ONLY when user specifically asks for whales or large holders. - Use "public_figure" ONLY when user asks for KOLs or popular figures. - Data with "sm", "whale", and "public_figure" is sparse — "whale" and "public_figure" are even sparser than "sm". Pairing any of these with other filters (volume, liquidity, netflow) is likely to return no results. - Only pair traderType="sm/whale/public_figure" with other filters (volume, liquidity, netflow) if the user request explicitly requires it. - Instead of pairing this with other filters, you can rely on orderBy to sort by netflow, volume, liquidity, etc. **CRITICAL WARNING:** 'priceChange' is NOT a valid filter. You cannot filter for "tokens up > 10%". Use `orderBy="priceChange"` instead. **Sorting Options** (orderBy field): Available fields (use with orderByDirection: "asc" or "desc"): - **priceUsd**: Sort by token price - **priceChange**: Sort by price change percentage - **marketCapUsd**: Sort by market capitalization - **volume**: Sort by total trading volume - **buyVolume**: Sort by buy volume - **sellVolume**: Sort by sell volume - **netflow**: Sort by net flow (buys - sells) - **liquidity**: Sort by DEX liquidity - **nofTraders**: Sort by number of traders (Note: Fields like `tokenAgeDays` or `outflowFdvRatio` are for FILTERING only, not sorting) Default: orderBy="netflow", orderByDirection="desc"
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    B
    maintenance
    Enables querying real-time and historical financial market data for stocks, options, forex, and crypto, including quotes, trades, technical indicators, and reference data through a set of MCP tools.
    Last updated
    3
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    A Model Context Protocol (MCP) server that provides onchain tools for Claude AI, allowing it to interact with the Polygon PoS blockchain to call contract functions, manage ERC20 tokens, and check gas prices.
    Last updated
    7
    6
    MIT

Matching MCP Connectors

  • Polygon.io stock/options/crypto: tickers, aggregates, news, splits, dividends.

  • Korean crypto + news (kpop/semi), 17 tools, signed receipts. x402 Base+Polygon+Solana.

  • Get comprehensive token screening data across multiple blockchain networks with advanced filtering. A maximum of 25 results are returned out of 1000s of tokens. Use the sorting and filtering options to narrow down the results. A maximum of 5 chains can be specified per request (excess chains are automatically trimmed). This tool helps with token discovery and finding trending tokens by combining different metrics: volume, liquidity, market cap, smart money activity, and token age. **IMPORTANT - Hyperliquid Special Case:** - Hyperliquid chain queries perpetual futures (perps), not spot tokens - When hyperliquid is mixed with other chains, two sections of up to 25 results each are returned - one for spot tokens and one for perps. - For perps, only these filters are supported: volume, buyVolume, sellVolume, openInterest, netflow, nofTraders, traderType - Additional orderBy fields for perps: openInterest, funding - Unsupported filters/orderBy will fallback to defaults INPUT EXAMPLES: # Find tokens which are going up in price. # Added some liquidity filter to remove spam and low quality tokens. ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "liquidity": {"from": 100000}, "nofTraders": {"from": 10}, "orderBy": "price_change", "orderByDirection": "desc" } ``` # Find top stablecoins by market cap ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["Stablecoin"], "orderBy": "market_cap_usd", "orderByDirection": "desc" } ``` # Find AI memecoins with high trading activity { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["AI Meme"], "liquidity": {"from": 100000}, "volume": {"from": 1000000} } # Find DeFi lending tokens { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "sectors": ["DeFi Lending (Money Markets)"], "netflow": {"from": 1000000} } # Find tokens which have a lot of buying activity (high nofBuyers and buyVolume) # Note that we added some filters to remove spam and low quality tokens. We added liquidity filter so that we only surface tokens which we can buy or sell. # We sort by `netflow` descending to get tokens with the most net buying activity. ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "24h", "liquidity": {"from": 100000}, "buyVolume": {"from": 1000000}, "marketCapUsd": {"from": 1000000}, "nofBuyers": {"from": 10}, "orderBy": "netflow", "orderByDirection": "desc" } ``` # Find Hyperliquid perps with high open interest and positive net flow ``` { "chains": ["hyperliquid"], "timeframe": "7d", "openInterest": {"from": 100000}, "volume": {"from": 1000000}, "netflow": {"from": 0}, "nofTraders": {"from": 10}, "orderBy": "netflow", "orderByDirection": "desc" } ``` WARNING: To avoid timeouts, it's recommended to: - Use 4 chains or less at a time (API tends to timeout with more chains) - Use shorter timeframes (e.g., 24h or 1h instead of 7d or 30d) Args: Returns: Comprehensive token metrics as markdown. Returns empty string if no tokens found. Columns returned: - **Token Address**: Token address (e.g., 0x1234567890123456789012345678901234567890) - **Symbol**: Token trading symbol (e.g., ETH, BTC, DOGE) - **Chain**: Blockchain network (ethereum, solana, polygon, etc.) - **Price USD**: Current token price in USD (currency formatted) - **Price Change**: Price change percentage over the date range (percentage, can be negative) - **Market Cap**: Current market capitalization (currency formatted) - **Fully Diluted Valuation (FDV)**: Market cap if all tokens were circulating (currency formatted) - **FDV/MC Ratio**: Ratio indicating how much supply is locked/vested (numeric, >1 means locked supply) - **USD Volume**: Total trading volume in USD (currency formatted) - **Buy USD Volume**: Total buy volume in USD (currency formatted) - **Sell USD Volume**: Total sell volume in USD (currency formatted) - **Net Flow USD**: Net flow (buys minus sells) in USD (currency formatted, can be negative) - **DEX Liquidity**: Available liquidity for trading (currency formatted) - **Inflow/FDV**: Inflow as percentage of FDV (percentage formatted) - **Outflow/FDV**: Outflow as percentage of FDV (percentage formatted) - **Token Age (Days)**: Days since token was first deployed - **Sectors**: List of token sectors/categories Hyperliquid perps columns (smart-money mode, when `onlySmartTradersAndFunds=true`): - **Net Position** (`LONG $X` / `SHORT $X` / `FLAT`): current net direction. Use this when answering long/short questions. - **Current Longs USD** / **Current Shorts USD**: gross notional on each side; sizing only, not direction. - **Net Position Change**: delta over the timeframe — can be positive while Net Position is still SHORT. Notes: - Positive Net Flow on spot tokens indicates more buying than selling - High FDV/MC Ratio suggests significant locked or vested tokens **Filtering Options** (filters parameter): - **Numeric Ranges**: volume, liquidity, marketCapUsd, netflow, tokenAgeDays, nofTraders, nofBuyers, nofSellers, nofBuys, nofSells, buyVolume, sellVolume, fdv, fdvMcRatio, inflowFdvRatio, outflowFdvRatio - **Categories**: sectors (e.g. ["AI", "Meme"]), includeSmartMoneyLabels - **Trader Type**: traderType (string: "all", "sm", "whale", "public_figure") - Use "sm" ONLY when user explicitly asks for "smart money". - Use "whale" ONLY when user specifically asks for whales or large holders. - Use "public_figure" ONLY when user asks for KOLs or popular figures. - Data with "sm", "whale", and "public_figure" is sparse — "whale" and "public_figure" are even sparser than "sm". Pairing any of these with other filters (volume, liquidity, netflow) is likely to return no results. - Only pair traderType="sm/whale/public_figure" with other filters (volume, liquidity, netflow) if the user request explicitly requires it. - Instead of pairing this with other filters, you can rely on orderBy to sort by netflow, volume, liquidity, etc. **CRITICAL WARNING:** 'priceChange' is NOT a valid filter. You cannot filter for "tokens up > 10%". Use `orderBy="priceChange"` instead. **Sorting Options** (orderBy field): Available fields (use with orderByDirection: "asc" or "desc"): - **priceUsd**: Sort by token price - **priceChange**: Sort by price change percentage - **marketCapUsd**: Sort by market capitalization - **volume**: Sort by total trading volume - **buyVolume**: Sort by buy volume - **sellVolume**: Sort by sell volume - **netflow**: Sort by net flow (buys - sells) - **liquidity**: Sort by DEX liquidity - **nofTraders**: Sort by number of traders (Note: Fields like `tokenAgeDays` or `outflowFdvRatio` are for FILTERING only, not sorting) Default: orderBy="netflow", orderByDirection="desc"
    Connector
  • What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).
    Connector
  • One-shot multi-band recall at a place (or lat/lng). Defaults to emem's standard at-a-glance band set; pass `band` / `bands` to override. Polygon-resolved places stay at the centroid by default (`n_cells: 1`) to keep multi-band calls cheap — pass `n_cells: 2..=64` to fan out. When to use: Use when the user names a place and wants the standard situational readout (vegetation + elevation + landcover + recent weather) without picking bands. Polygon-aware: `place` that resolves to a polygon (park, lake, district) lands at the centroid unless `n_cells` widens it. For a single band, use the domain-specific shortcuts (emem_ndvi, emem_air, …) or emem_recall directly.
    Connector
  • "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). `since` accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.
    Connector
  • Per-field agricultural-boundary polygons from the Fields of The World global product (~3.17B fields, 241 countries, 10 m resolution, CC-BY-4.0). Returns a GeoJSON FeatureCollection with the polygon geometries, FIBOA-compatible properties, and a planar `area_m2` per field — plus provenance (source CID, provider URL, license, attribution). When to use: Call when the user asks about farms, fields, parcels, croplands, plots, or agricultural boundaries inside a region — anywhere the OSM/Nominatim boundary alone is too coarse (the OSM polygon for a farm is its estate envelope; this returns the individual field polygons inside). Pass `place` (free-text) or `polygon_bbox`. For farms wider than ~10 km², split the bbox: the fetcher caps each call at 16 covering tiles. The receipt quotes `license: CC-BY-4.0` and `attribution: Fields of The World / Taylor Geospatial Institute` — surface both with any rendered map. For a one-shot "facts at every cell inside the farm PLUS the field polygons", call `emem_recall_polygon` with `include: ["ftw_fields"]` instead.
    Connector
  • Recall Sentinel-2 NDVI (indices.ndvi, 10 m native) at a point or place. Composes locate → cell64 → recall in one call; auto-materializes on miss. When to use: Use when the user names a place (or lat/lng) and just wants the NDVI number. Polygon-resolved places default to a 16-cell fan-out aggregated as mean/median. Set `n_cells: 1` for point behaviour. For multi-band batches use emem_recall.
    Connector
  • REQUIRES one of `event` (single-event mode) OR `topic` (cross-event mode) — call with no args fails. Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). `topic` (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}.
    Connector
  • [SPEND: 5 USDC] Generate a short-form video from a prompt or URL. Costs 5 USDC (Base/Ethereum/Polygon/Solana via x402). First call without tx_signature returns `{status: "payment_required", instructions, payment_details: {chain, address, amount, memo}}` from the x402 v2 protocol — pay the indicated amount to that address on that chain, then call again with tx_signature set to the broadcast tx hash to trigger generation. Returns a session_id to poll with check_video_status. Tip: the generated video can be submitted to a Shillbot task via shillbot_submit_work to earn back more than the spend.
    Connector
  • Send or record bounded PP0 test POL for Polygon Amoy gas. Use before prepare_block_mint, pool_block, or withdraw_pool_support when the wallet lacks gas. Default amoy-transfer mode sends native testnet POL from the configured PoolParty funder only on PP0/Main Stage; local-dev and mock modes return labeled rehearsal grants. Public wallet bootstrap action. No MCP auth required.
    Connector
  • Honeypot, rug-pull, and scam detection for any EVM token. Returns a 0–100 risk score with labeled flags: honeypot status, hidden ownership, mint authority, self-destruct, buy/sell tax rates, creator wallet concentration, and open-source status. Covers 40+ chains (Ethereum, Base, BSC, Arbitrum, Polygon, Solana, etc.) via GoPlusLabs. Useful pre-trade before buying unknown tokens, before routing payments through new contracts, or when validating DeFi protocol addresses. Pairs with solana-token-risk (Solana-native rug detection) and market-intelligence (endpoint verification).
    Connector
  • Deploy an ERC-20 token on mainnet or testnet using your agent's own wallet. Returns encoded calldata (to, value, data) — your agent signs and broadcasts the transaction, paying gas + $10 fee directly from its wallet. Same contract and fee flow as human users on the website. Your agent owns the deployed contract from the moment of deploy. Works on Ethereum, Base, BNB Chain, Polygon, and Sepolia testnet. After broadcasting the tx, call ava_confirm_deployment with the txHash to resolve the contract address. Use ava_simulate_token first to validate config and estimate fees without spending gas.
    Connector
  • List all 16 chains supported by this LayerZero MCP server with their Endpoint IDs (EIDs). Includes Ethereum, Arbitrum, Optimism, Polygon, BSC, Avalanche, Base, Solana, zkSync, Sei, Sonic, Berachain, Story, Monad, MegaETH, and Tron. EIDs are used in EndpointV2.quote() and EndpointV2.send() to identify destination chains.
    Connector
  • Cell polygon as a native MCP EmbeddedResource (mimeType application/geo+json). Properties carry centre lat/lng, bbox, approx size in metres, and the 8-cell neighbourhood — drop straight into Mapbox / Leaflet / Deck.gl / QGIS without a GIS pipeline. When to use: Call when the agent (or a downstream renderer) needs the cell as geographic geometry — for map overlays, polygon-clipping ops, or feeding a styling pipeline. Pass `cell` as cell64 or place name. The result is a GeoJSON Feature with Polygon geometry; for a FeatureCollection that includes every recalled fact's value as a property, fetch /v1/cells/{cell64}/recall_geojson?bands=... over plain REST instead.
    Connector
  • Scan Kimchi Premium for ALL tokens (180+) traded on both Upbit and Binance. Returns token-by-token premium %, reverse premiums (negative = Korean discount), Upbit vs Bithumb price gaps, market share between exchanges. Each token includes warning flags, volume soaring alerts, deposit soaring alerts. Updated every 60 seconds. Essential for cross-exchange arbitrage analysis. 💰 Price: $0.01 USDC per call 💳 Payment: x402 micropayment on Base, Polygon, or Solana 🔧 Client: AgentCash, Pay.sh, or any x402 SDK 📖 Docs: https://api.printmoneylab.com/.well-known/x402
    Connector