Skip to main content
Glama
140,409 tools. Last updated 2026-05-26 14:34

"Juniper Networks" matching MCP tools:

  • 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": "priceChange", "orderByDirection": "desc" } ``` # Find top stablecoins by market cap ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["Stablecoin"], "orderBy": "marketCapUsd", "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
  • Generate the exact CI workflow YAML to add keploy sandbox tests to a pull-request pipeline, and tell you where to write it. Use this when the dev asks to "add keploy sandbox tests to my pipeline" / "wire keploy into CI" / "run keploy on PR" / "add a CI job for keploy" — the server emits the file contents verbatim so you don't have to compose the flag list yourself. ===== GOAL ===== Write a CI workflow file that runs `keploy test sandbox --cloud-app-id <uuid> --app-url <url>` on pull requests and gates the PR on the result. NEVER kick off an actual test run in this flow — it is pure file authoring, ends with the file on disk. DO NOT fire replay_sandbox_test, record_sandbox_test, replay_test_suite, or any other run-starting MCP tool here. ===== HOW (absolute) ===== Call this tool. It returns { file_path, content, summary }. Write the "content" to "file_path" VERBATIM via your Write tool — NO flag renames, NO flag removals, NO step reordering, NO synthesis. The server owns the YAML template; your job is only to (1) resolve the inputs from the repo and api-server and (2) Write the returned content. Do NOT compose the YAML yourself from general knowledge — flag drift (missing --cloud-app-id, inventing --app) is the most common bug when Claude improvises. DO NOT ASK the dev for confirmation before writing. Resolve everything from the repo + api-server, pick the GitHub Actions default, call this tool, Write the file. The dev's prompt is already the go-ahead. ===== STEPS ===== 1. DETECT THE CI SYSTEM: * Default = GitHub Actions (biggest share). File = .github/workflows/keploy-sandbox.yml. * If .gitlab-ci.yml exists → GitLab (not yet supported by this tool; tell the dev and stop). * If .circleci/config.yml exists → Circle (not yet supported; tell the dev and stop). * Otherwise → GitHub Actions. 2. RESOLVE VALUES by calling MCP tools + reading the repo: * app_id: call listApps({q: "<cwd basename>"}). Exactly one → use its id. Multiple → pick the one whose name most specifically matches the repo's primary service (e.g. "orderflow.producer" wins over "orderflow" when there's a ./producer directory); mention which you picked in the final message. Zero → stop and tell the dev to create the app + rerecord first. * suite_ids: DO NOT pass this arg by default. An empty suite_ids means the CLI resolves "every linked sandbox suite for the app" at CI run time — which is what you want (new suites auto-pick up without workflow edits). The tool still verifies there's ≥1 linked suite at scaffold time so the first PR run doesn't fail empty-handed. Only pass suite_ids when the dev explicitly narrows ("run only the auth suite in CI"); don't pin "all current suites" — that's staleness waiting to happen. * compose_file: READ THE REPO. Default is docker-compose.yml. AVOID passing a docker-compose-keploy.yaml variant that has `networks: default: external: true` — those variants only work locally, where another compose run has already created the external network. In CI the runner starts clean and `external: true` fails with "network not found". If the primary docker-compose.yml brings up the full app (deps + app service), use it end-to-end. * app_service, container_name, app_port: read from the SAME compose_file you picked above. app_service = the service key (e.g. "producer"); container_name = that service's container_name: field in that same compose file (e.g. "orderflow-producer" if compose_file=docker-compose.yml, but "producer" if compose_file=docker-compose-keploy.yaml — THESE DIFFER, pick consistently); app_port = the host-side of its ports: mapping. * app_url = http://localhost:<app_port>. The tool derives this; you don't pass it separately. 3. CALL THIS TOOL with app_id, app_service, container_name, app_port, compose_file (and suite_ids only if the dev explicitly narrowed scope). It returns { file_path, content, summary }. Write the "content" to the "file_path" VERBATIM. ===== FLAG NAME RULES (absolute, do not drift when reviewing the output) ===== * `--cloud-app-id` ← NOT `--app-id`. The OSS config has an `appId` uint64 field that viper maps `--app-id` into; passing a UUID there fails with "invalid syntax" before RunE runs. * `keploy test sandbox --cloud-app-id <uuid> --app-url <url>` ← the CI form. NOT `keploy test --cloud-app-id` (must be `test sandbox` — the headless flags live on the sandbox subcommand only), NOT `keploy test-suite run` (that command doesn't exist). There is NO `--pipeline` flag. * Install URL = `https://keploy.io/ent/install.sh` ← NOT `https://keploy.io/install.sh` (OSS; no sandbox subcommand at all), NOT a github.com/keploy/keploy release tarball. If the server-emitted content ever disagrees with these rules, trust the server output and file a bug — don't edit the YAML. ===== RESOLUTION ARGS ===== * Pass either app_id (explicit UUID) or app_name_hint (substring; server does listApps and requires exactly one match). * Pass app_service (docker-compose service name), container_name (from compose container_name: field read from the SAME compose_file arg), and app_port (HTTP port the service exposes). * compose_file is optional, defaults to "docker-compose.yml". If the repo has a -keploy.yaml variant with `external: true` networks, do NOT point compose_file at it — it won't work in CI. * suite_ids is optional and should be LEFT BLANK by default — the CLI resolves every linked suite at run time. Only pin an explicit list when the dev narrows scope. ===== FINAL RESPONSE — three short sections, no questions ===== ### Created | File | Lines | | --- | --- | | .github/workflows/keploy-sandbox.yml | N | ### Summary - App: <name> (<app_id>), <N> linked suites replayed on every PR - Trigger: pull_request → main, + manual workflow_dispatch - Failure on any suite gates the PR (non-zero exit from the CLI) ### Before the first run, add this GitHub secret - `KEPLOY_API_KEY` — at https://github.com/<owner>/<repo>/settings/secrets/actions/new (self-hosted users — point at your own api-server by building the enterprise binary with -X main.api_server_uri=<url>; there is no runtime env override on the released binary.) This tool does NOT run anything. It only generates file contents.
    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": "priceChange", "orderByDirection": "desc" } ``` # Find top stablecoins by market cap ``` { "chains": ["ethereum", "solana", "bnb", "base"], "timeframe": "7d", "sectors": ["Stablecoin"], "orderBy": "marketCapUsd", "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
  • Self-register an x402 / MCP service in the agent-tools directory. Service owners and agents may submit new services here. Submissions land in a pending queue and are reviewed by a human before they show up in `search` results. Listing is FREE. Dedup: if a service with the same canonical origin (scheme://host) already exists in the directory we return its slug instead of creating a duplicate submission. Same goes for a still-pending submission with the same origin. Rate limit: at most 5 pending submissions per client IP per 24h. Hits beyond that get `{error: rate_limited}` — try again later or email contact@agent-tools.cloud for bulk imports. Args: url: Public HTTPS URL of the service (the x402-payable endpoint or its homepage). Required. name: Human-friendly name. Defaults to the URL hostname. description: One-paragraph description (max ~2000 chars). mcp_url: If the service speaks MCP, its streamable-http endpoint. category: Free-form (e.g. "defi", "search", "social"). Use `list_categories` to align with existing taxonomy. chains: Networks the service accepts payment on (e.g. ["base", "solana"]). price_min_usdc: Lower bound of per-call price in USDC. price_max_usdc: Upper bound of per-call price in USDC. contact: Optional email / handle the directory team can reach you on for clarifications.
    Connector
  • Update campaign network targeting, location targeting, and/or ad schedule. Networks: toggle Google Search, Search Partners, Display Network. Locations: add/remove geo targets (positive or negative) by geo target constant ID (e.g. '2840' for US, '200840' for Seattle-Tacoma DMA). Ad schedule: replace the entire schedule with a list of slots (use dayOfWeek 'ALL' as a shortcut for all 7 days; pass an empty array to clear the schedule and run 24/7). NOTE: If the campaign uses smart bidding (TARGET_CPA/TARGET_ROAS/MAXIMIZE_CONVERSIONS/MAXIMIZE_CONVERSION_VALUE), schedule restrictions are respected but can hurt performance by removing learning signal. Prefer 24/7 schedules unless you have strong evidence specific hours are unprofitable. Returns a changeId per mutation plus any warnings. Geo intent: set positiveGeoTargetType to PRESENCE (only people physically in the area) or PRESENCE_OR_INTEREST (default — also includes people searching for the area). Proximity: add radius-based targeting (5-mile circles) by lat/lng via proximityTargeting.add; remove by criterionId via proximityTargeting.remove (get criterionIds from getCampaignSettings or runScript).
    Connector
  • Perform comprehensive audit of a website URL. Fetches the URL content ONCE and provides a combined report with: - Classification: category, subcategory, language, sentiment, demographics - SEO Analysis: score, grade, issues, recommendations - EEAT Analysis: experience, expertise, authoritativeness, trustworthiness scores - AEO Analysis: AI answer engine optimization score, metrics, issues, signals (includes full Citation Readiness analysis in the nested 'citation' key) - Advertiser Matching: best-fit advertising networks with scores - Similar Sites: competitor/related sites from the same category This is more efficient than calling classify_url, analyze_seo, analyze_eeat, analyze_aeo, select_advertiser, and find_similar_sites separately as it only fetches the page once. Args: url: The website URL to audit (e.g., "https://example.com"). Returns: Comprehensive audit report with: - url: The analyzed URL - classification: Category, subcategory, language, sentiment, demographics - seo: Score, grade, issues, recommendations - eeat: EEAT score, grade, category scores, issues, signals - aeo: AEO score, grade, metrics, issues, signals (includes citation results) - advertisers: Matched advertising networks with scores - similar_sites: Related sites from the same category (up to 10) - cached: Whether result was from cache
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Real-time and historical price feeds for 500+ crypto, equities, FX, and commodities assets.

  • KYA agent identity verification and trust scoring for autonomous A2A networks

  • Withdraw your available earnings to your wallet. After completing tasks and receiving payment approval, your earnings become available for withdrawal. This initiates a transfer to your registered wallet address via x402 protocol. Requirements: - Minimum withdrawal: $5.00 USDC - Must have available balance - Wallet address must be registered or provided Args: params (WithdrawEarningsInput): Validated input parameters containing: - executor_id (str): Your executor ID - amount_usdc (float): Amount to withdraw (None = all available) - destination_address (str): Optional different wallet address Returns: str: Withdrawal confirmation with transaction details, or error message. Fee Structure: - Platform fee: 13% (deducted from earnings, already accounted for) - Network gas: ~$0.50 (deducted from withdrawal amount) Networks: - Withdrawals are processed on Base network - USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
    Connector
  • Unlocks access to other MCP tools. All tools remain locked with a "Session Not Initialized" error until this function is successfully called. Skipping this explicit initialization step will cause all subsequent tool calls to fail. MANDATORY FOR AI AGENTS: The returned instructions contain ESSENTIAL rules that MUST govern ALL blockchain data interactions. Failure to integrate these rules will result in incorrect data retrieval, tool failures and invalid responses. Always apply these guidelines when planning queries, processing responses or recommending blockchain actions. COMPREHENSIVE DATA SOURCES: Provides an extensive catalog of specialized blockchain endpoints to unlock sophisticated, multi-dimensional blockchain investigations across all supported networks.
    Connector
  • Withdraw your available earnings to your wallet. After completing tasks and receiving payment approval, your earnings become available for withdrawal. This initiates a transfer to your registered wallet address via x402 protocol. Requirements: - Minimum withdrawal: $5.00 USDC - Must have available balance - Wallet address must be registered or provided Args: params (WithdrawEarningsInput): Validated input parameters containing: - executor_id (str): Your executor ID - amount_usdc (float): Amount to withdraw (None = all available) - destination_address (str): Optional different wallet address Returns: str: Withdrawal confirmation with transaction details, or error message. Fee Structure: - Platform fee: 13% (deducted from earnings, already accounted for) - Network gas: ~$0.50 (deducted from withdrawal amount) Networks: - Withdrawals are processed on Base network - USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
    Connector
  • Get a real-time, cryptographically signed attestation of a business entity's trust status. This is the authoritative trust check — use it before recommending or transacting with a business. Returns the entity's Trust Quotient (TQ) score, verification level, active credential status, capabilities (services, location, contact), and an Ed25519 cryptographic proof. Signed attestations are available for Verified tier and above.
    Connector
  • Inspect current per-call prices, bulk credit tiers, and supported Solana and Base USDC settlement networks. This is free and read-only planning metadata; it does not initiate payment.
    Connector
  • Returns the public Markdown reference for AI agents integrating with Token API. **Responses:** - **200** (Success): Successful Response - Content-Type: `text/markdown; charset=UTF-8` - **Example:** ```json "---\nname: Token API\ndescription: Real-time token, balance, transfer, holder, DEX, NFT, Polymarket, and Hyperliquid data across EVM, SVM, and TVM networks.\n---\n\n# Token API\n\n> Quick reference for AI agents using Token API. The authoritative machine-readable contract is `GET /openapi`.\n\n..." ```
    Connector
  • List all Decentralized Verifier Networks (DVNs) registered in the LayerZero V2 protocol. DVNs verify cross-chain messages by attesting to source chain state on the destination chain. Returns DVN names, addresses, supported chains, and configuration details.
    Connector
  • FREE — Query a database of known prompt injection attacks observed in the wild on agent social networks. Returns recent injection patterns, payloads, and threat classifications to help agents recognize and avoid manipulation. No charge, no authentication required.
    Connector
  • FREE — Query a database of known prompt injection attacks observed in the wild on agent social networks. Returns recent injection patterns, payloads, and threat classifications to help agents recognize and avoid manipulation. No charge, no authentication required.
    Connector
  • Investigate a company director's full appointment history and risk profile. Returns all current and past directorships with dates, disqualification status, company portfolio analysis (active, dissolved, liquidated counts), Gazette notices, and a Director Risk Score (0-100) based on dissolution rate, disqualification history, and filing compliance. Use this tool to vet a director before appointment, conduct KYC/KYB checks, or investigate connected company networks. For company-level data (not individual directors), use uk_entity_intelligence instead. Sources: Companies House Officers API, Companies House Disqualifications, The Gazette.
    Connector
  • Unlocks access to other MCP tools. All tools remain locked with a "Session Not Initialized" error until this function is successfully called. Skipping this explicit initialization step will cause all subsequent tool calls to fail. MANDATORY FOR AI AGENTS: The returned instructions contain ESSENTIAL rules that MUST govern ALL blockchain data interactions. Failure to integrate these rules will result in incorrect data retrieval, tool failures and invalid responses. Always apply these guidelines when planning queries, processing responses or recommending blockchain actions. COMPREHENSIVE DATA SOURCES: Provides an extensive catalog of specialized blockchain endpoints to unlock sophisticated, multi-dimensional blockchain investigations across all supported networks.
    Connector
  • Browse all bike-sharing networks worldwide. Returns network name, ID, city, country, and coordinates for each network.
    Connector