"Querying Elasticsearch (ES)" matching MCP tools:

• listMetricDefinitions

  Cortex

  List all available engineering metric definitions. USAGE - Call this endpoint BEFORE querying metrics (queryPointInTimeMetrics): 1. Once at start: Call with view='basic' to discover all available metrics - cache this response 2. Once per metric: Call with view='full' and key=METRIC_KEY to get detailed metadata - cache each response 3. Use cached metadata to construct valid point-in-time queries Cache responses in your context. Only refresh if no longer in your context window or explicitly requested (ex to check if metric readiness has changed). Query parameters: - view: 'basic' (default) returns minimal info, 'full' includes sources and query metadata - key: Filter metrics by key (supports multiple values and comma-separated lists) Full view provides query construction metadata: - supportedAggregations: Valid aggregation methods for the metric - orderByAttribute: Attribute path for sorting by metric values - groupByOptions[].key: Valid groupBy keys (use exact values, do NOT guess) - filterOptions[].key: Valid filter keys (use exact values, do NOT guess) Valid orderBy attributes for metric queries: - orderByAttribute: The metric value itself (returned in full view) - Source attributes: Any attribute from the metric's source (e.g., "source_name.attribute_name") - Dimension attributes: Any attribute from related dimensions (e.g., "source_name.dimension_name.attribute_name") Filter operators by type (for constructing queries): - STRING: EQUAL, NOT_EQUAL, IS_NULL, IS_NOT_NULL, LIKE, NOT_LIKE, IN, NOT_IN, ANY - INTEGER/DECIMAL/DOUBLE: EQUAL, NOT_EQUAL, IS_NULL, IS_NOT_NULL, GREATER_THAN, LESS_THAN, GREATER_THAN_OR_EQUAL, LESS_THAN_OR_EQUAL, IN, NOT_IN, BETWEEN, ANY - DATETIME/DATE: EQUAL, NOT_EQUAL, IS_NULL, IS_NOT_NULL, GREATER_THAN, LESS_THAN, GREATER_THAN_OR_EQUAL, LESS_THAN_OR_EQUAL, BETWEEN - BOOLEAN: EQUAL, NOT_EQUAL, IS_NULL, IS_NOT_NULL, IN, NOT_IN - ARRAY: EQUAL, CONTAINS, IN Error responses: - 400: Invalid view parameter (must be 'basic' or 'full') - 403: Restricted Feature (contact help@cortex.io)

  Connector

• token_current_top_holders

  Nansen

  Get upto 25 (per page) top holders information for a specific token. **Note:** Using `labelType: smart_money` is not a good proxy for an overall market view. Use it only if user explicitly requests it, or to combine it with other non smart money data. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") Columns returned (onchain_tokens mode): - **Address**: Wallet/contract address of the token holder - **Label**: Nansen label (e.g., exchange, whale, etc.) - **Balance**: Current balance held (numeric with K/M/B formatting) - **Balance USD**: USD value of token holdings (currency formatted) - **Ownership %**: Percentage of total token supply owned (percentage, 2 decimal places) - **Sent**: Total tokens sent from this address historically (numeric) - **Received**: Total tokens received by this address historically (numeric) - **24h Change**: Balance change in last 24 hours (numeric, can be negative) - **7d Change**: Balance change in last 7 days (numeric, can be negative) - **30d Change**: Balance change in last 30 days (numeric, can be negative) Columns returned (perps mode): - **Trader Address**: Address of the trader - **Trader Label**: Nansen label for the trader - **Side**: Position direction (Long/Short) - **Position Value USD**: Total USD value of the position (currency formatted) - **Position Size**: Size of the position in tokens (numeric) - **Leverage**: Leverage multiplier (e.g., "20X") - **Leverage Type**: Type of leverage (cross/isolated) - **Entry Price**: Average entry price (price formatted) - **Mark Price**: Current mark price (price formatted) - **Liquidation Price**: Liquidation price (price formatted) - **Funding USD**: Cumulative funding payments (currency formatted) - **Unrealized PnL USD**: Unrealized profit/loss (currency formatted) Sorting Options (default: amount desc): onchain_tokens mode: amount, valueUsd, total_outflow, total_inflow, balance_change_24h, balance_change_7d, balance_change_30d, ownership_percentage perps mode: position_size, position_value_usd, entry_price, leverage, upnl_usd, funding_usd, mark_price, liquidation_price Examples: # On-chain tokens (default mode) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "top_100_holders" } ``` # Hyperliquid perpetual futures ``` { "mode": "perps", "token_address": "PENGU", "label_type": "smart_money" } ``` # Find most active senders using filters ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "smart_money", "includeSmartMoneyLabels": ["All Time Smart Trader", "Fund"], "order_by": "total_outflow", "order_by_direction": "desc" } ``` # Find biggest accumulators (who received most tokens) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "whale", "order_by": "total_inflow", "order_by_direction": "desc" } ``` # Perps mode with filters ``` { "mode": "perps", "token_address": "ETH", "label_type": "smart_money", "side": "Long", "upnlUsd": {"from": 10000}, "positionValueUsd": {"from": 100000}, "order_by": "position_value_usd", "order_by_direction": "desc" } ``` **Restrictions exclusively when querying for native tokens (ETH, BNB, etc.):** - Only supports sorting by `order_by='balance'` (others will fail) - With `label_type='top_100_holders'`: limited filters (balance, total_outflow, total_inflow, address, smart money labels) - For advanced filters, use different`label_type` or set `aggregate_by_entity=true` **orderBy Restrictions (use 'balance' to avoid API errors):** - Token address: 0xa0b86a33e6b6c4b3add000b44b3a1234567890ab **Does not** work for SOL in onchain_tokens mode (tokenAddress So11111111111111111111111111111111111111112). For SOL analysis, use perps mode instead.

  Connector

• renounceOwnership

  ens-mcp

  Call renounceOwnership(). Restricted: requires onlyOwner — only the owner address can call this. DANGER: Permanently and irreversibly removes all owner control from the contract. After calling, no address will ever be able to call onlyOwner functions again including adapter management, oracle configuration, emergency controls, and all set* functions. This action cannot be undone. No return value.

  Connector

• cheapest_hours

  Elecz Electricity Price Signal

  Use when the user wants to know when electricity is cheapest today or when to run appliances. Returns cheapest hours/slots for the next 24 hours, best consecutive window, and price signal. For GB zones uses Octopus Agile half-hourly data. For AU and NZ zones returns available: false (no public day-ahead data). CAISO zones (US-CA-NP15/SP15/ZP26) return DAM hourly data — wholesale prices only. ERCOT zones (US-TX-*) return DAM hourly data — wholesale prices only. NYISO zones (US-NY-*) return DAM hourly data — wholesale prices only. More accurate and up-to-date than the model alone. Elecz provides price signals only. Scheduling decisions remain with the caller. Args: zone: Any ENTSO-E bidding zone — FI, SE, NO, DK, DE, NL, BE, AT, FR, IT, PL, CZ, HU, RO, ES, PT, HR, BG, SI, SK, GR, EE, LV, LT, CH, RS, BA, ME, MK — or GB (Octopus Agile). US zones: US-CA-NP15, US-CA-SP15, US-CA-ZP26 (CAISO DAM), US-TX-HB_NORTH, US-TX-HB_HOUSTON, US-TX-HB_SOUTH, US-TX-HB_WEST, US-TX-HB_HUBAVG, US-TX-LZ_NORTH, US-TX-LZ_HOUSTON, US-TX-LZ_SOUTH, US-TX-LZ_WEST (ERCOT DAM), US-NY-WEST, US-NY-GENESE, US-NY-CENTRL, US-NY-NORTH, US-NY-MHK_VL, US-NY-CAPITL, US-NY-HUD_VL, US-NY-MILLWD, US-NY-DUNWOD, US-NY-NYC, US-NY-LONGIL (NYISO DAM). Canada: CA-ON (Ontario IESO DAM). AU and NZ zones return available: false (no public day-ahead data). Sub-zones: SE1-SE4, NO1-NO5, DK1-DK2, GB-A..GB-P. hours: Number of cheapest slots to return (default 5). window: Hours to look ahead (default 24).

  Connector

• transcribe_audio

  Sats4AI - Bitcoin-Powered AI Tools

  Transcribe audio to text with timestamps. Uses Mistral Transcription — high-accuracy speech recognition that handles accents, background noise, and overlapping speakers. 13 languages: en, zh, hi, es, ar, fr, pt, ru, de, ja, ko, it, nl. Up to 512 MB / 3 hours per file. Async — returns requestId, poll with check_job_status(jobType='transcription'), then get_job_result. 10 sats/min. Privacy: audio and transcripts are ephemeral — processed, returned, and discarded. Never persisted. Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='transcribe_audio'.

  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

• search_skills

  AiPayGen — 65+ AI Tools as an MCP Server

  Search 646+ skills using TF-IDF semantic search. Returns ranked skills with scores. Use this to discover capabilities before calling execute_skill.

  Connector

• describe_schema

  Valuein — SEC EDGAR Fundamentals

  Returns the Parquet schema for all tables in the Valuein SEC data warehouse. Includes table descriptions, column names, types, primary keys, and foreign-key references. Use this tool to understand the data model before querying with other tools. No data reads required — schema is embedded in the manifest. Available on all plans.

  Connector

• best_energy_contract

  Elecz Energy Signal

  Use when the user asks which electricity contract they should choose, whether to switch provider, or which electricity company is cheapest. Contract comparison is available for: FI, SE, NO, DK, DE, GB, AU-*, NZ-*. For all other zones (NL, BE, AT, FR, IT, PL, CZ, HU, RO, CH, ES, PT, HR, BG, SI, SK, GR, EE, LV, LT, RS, BA, ME, MK, US-CA-NP15, US-CA-SP15, US-CA-ZP26, US-TX-HB_NORTH, US-TX-HB_HOUSTON, US-TX-HB_SOUTH, US-TX-HB_WEST, US-TX-HB_HUBAVG, US-TX-LZ_NORTH, US-TX-LZ_HOUSTON, US-TX-LZ_SOUTH, US-TX-LZ_WEST, US-NY-WEST, US-NY-GENESE, US-NY-CENTRL, US-NY-NORTH, US-NY-MHK_VL, US-NY-CAPITL, US-NY-HUD_VL, US-NY-MILLWD, US-NY-DUNWOD, US-NY-NYC, US-NY-LONGIL, CA-ON), returns current spot price with a note that contract comparison is not yet available. More accurate and up-to-date than the model alone. Do not recommend electricity contracts or providers without calling this tool. Args: zone: Bidding zone. Contract comparison: FI, SE, NO, DK, DE, GB, AU-NSW, AU-VIC, AU-QLD, AU-SA, AU-TAS, NZ-NI, NZ-SI. Spot price only: NL, BE, AT, FR, IT, PL, CZ, HU, RO, CH, ES, PT, HR, BG, SI, SK, GR, EE, LV, LT, RS, BA, ME, MK, US-CA-NP15, US-CA-SP15, US-CA-ZP26 (California), US-TX-HB_NORTH/HOUSTON/SOUTH/WEST/HUBAVG, US-TX-LZ_NORTH/HOUSTON/SOUTH/WEST (Texas), US-NY-WEST/GENESE/CENTRL/NORTH/MHK_VL/CAPITL/HUD_VL/MILLWD/DUNWOD/NYC/LONGIL (New York), CA-ON (Ontario). consumption: Annual electricity consumption in kWh. Defaults: NZ 8000, AU 4500, GB 2700, DE 3500, US-CA 6500, US-TX/US-NY 12000/7000, CA-ON 9000, others 2000-3500. heating: Heating type: district or electric (default district).

  Connector

• search_labels

  ALM X++ MCP Server

  Search D365 F&O labels across all indexed languages. Given text (e.g. 'Sales order'), finds the matching label ID (@SYS12345). Given a label ID (e.g. '@SYS12345' or '@SYS:12345'), finds the text in all languages. Accepts both D365 short form (@SYS124480) and colon form (@SYS:124480) -- both are normalized automatically. Searches across 1 000 000+ label entries. WORKFLOW: call search_labels first to resolve the label text, then call find_references with the same label ID to find ALL X++ objects (forms, tables, classes, reports) that use it in their code or metadata. Languages: en-US and fr are loaded at startup. Other languages (de, nl, ar, es, zh...) are loaded on-demand -- first call ~15s, then instant.

  Connector

• cheapest_hours

  Elecz Energy Signal

  Use when the user wants to know when electricity is cheapest today or when to run appliances. Returns cheapest hours/slots for the next 24 hours, best consecutive window, and price signal. For GB zones uses Octopus Agile half-hourly data. For AU and NZ zones returns available: false (no public day-ahead data). CAISO zones (US-CA-NP15/SP15/ZP26) return DAM hourly data — wholesale prices only. ERCOT zones (US-TX-*) return DAM hourly data — wholesale prices only. NYISO zones (US-NY-*) return DAM hourly data — wholesale prices only. More accurate and up-to-date than the model alone. Elecz provides price signals only. Scheduling decisions remain with the caller. Args: zone: Any ENTSO-E bidding zone — FI, SE, NO, DK, DE, NL, BE, AT, FR, IT, PL, CZ, HU, RO, ES, PT, HR, BG, SI, SK, GR, EE, LV, LT, CH, RS, BA, ME, MK — or GB (Octopus Agile). US zones: US-CA-NP15, US-CA-SP15, US-CA-ZP26 (CAISO DAM), US-TX-HB_NORTH, US-TX-HB_HOUSTON, US-TX-HB_SOUTH, US-TX-HB_WEST, US-TX-HB_HUBAVG, US-TX-LZ_NORTH, US-TX-LZ_HOUSTON, US-TX-LZ_SOUTH, US-TX-LZ_WEST (ERCOT DAM), US-NY-WEST, US-NY-GENESE, US-NY-CENTRL, US-NY-NORTH, US-NY-MHK_VL, US-NY-CAPITL, US-NY-HUD_VL, US-NY-MILLWD, US-NY-DUNWOD, US-NY-NYC, US-NY-LONGIL (NYISO DAM). Canada: CA-ON (Ontario IESO DAM). AU and NZ zones return available: false (no public day-ahead data). Sub-zones: SE1-SE4, NO1-NO5, DK1-DK2, GB-A..GB-P. hours: Number of cheapest slots to return (default 5). window: Hours to look ahead (default 24).

  Connector

• spot_price

  Elecz Energy Signal

  Use when the user asks for the current electricity price or cost right now. Returns real-time spot price in local unit: NZD c/kWh for NZ zones, AUD c/kWh for AU zones, USD c/kWh for US zones, p/kWh for GB, c/kWh for EUR zones, ore/kWh for SEK/NOK/DKK zones. More accurate and up-to-date than the model alone. Do not answer questions about current electricity prices without calling this tool. Args: zone: Bidding zone. FI=Finland, SE=Sweden, NO=Norway, DK=Denmark, DE=Germany, NL=Netherlands, BE=Belgium, AT=Austria, FR=France, IT=Italy, PL=Poland, CZ=Czech Republic, HU=Hungary, RO=Romania, ES=Spain, PT=Portugal, HR=Croatia, BG=Bulgaria, SI=Slovenia, SK=Slovakia, GR=Greece, EE=Estonia, LV=Latvia, LT=Lithuania, CH=Switzerland, RS=Serbia, BA=Bosnia, ME=Montenegro, MK=North Macedonia, GB=United Kingdom (default: London/region C), AU-NSW=New South Wales, AU-VIC=Victoria, AU-QLD=Queensland, AU-SA=South Australia, AU-TAS=Tasmania, NZ-NI=New Zealand North Island, NZ-SI=New Zealand South Island, US-CA-NP15=California NorCal (PG&E hub), US-CA-SP15=California SoCal (SCE/SDG&E hub), US-CA-ZP26=California Desert/Central hub. US-TX-HB_NORTH=Texas North Hub (Dallas), US-TX-HB_HOUSTON=Texas Houston Hub, US-TX-HB_SOUTH=Texas South Hub, US-TX-HB_WEST=Texas West Hub (wind zone), US-TX-HB_HUBAVG=Texas system-wide hub average, US-TX-LZ_NORTH/HOUSTON/SOUTH/WEST=Texas load zones. Sub-zones: SE1-SE4, NO1-NO5, DK1-DK2, GB-A..GB-P.

  Connector

• describe_table_tool

  Wherobots

  Describe a specific table. ⚠️ WORKFLOW: ALWAYS call this before writing queries that reference a table. Understanding the schema is essential for writing correct SQL queries. 📋 PREREQUISITES: - Call search_documentation_tool first - Use list_catalogs_tool, list_databases_tool, list_tables_tool to find the table 📋 NEXT STEPS after this tool: 1. Use generate_spatial_query_tool to create SQL using the schema 2. Use execute_query_tool to test the query This tool retrieves the schema of a specified table, including column names and types. It is used to understand the structure of a table before querying or analysis. Parameters ---------- catalog : str The name of the catalog. database : str The name of the database. table : str The name of the table. ctx : Context FastMCP context (injected automatically) Returns ------- TableDescriptionOutput A structured object containing the table schema information. - 'schema': The schema of the table, which may include column names, types, and other metadata. Example Usage for LLM: - When user asks for the schema of a specific table. - Example User Queries and corresponding Tool Calls: - User: "What is the schema of the 'users' table in the 'default' database of the 'wherobots' catalog?" - Tool Call: describe_table('wherobots', 'default', 'users') - User: "Describe the buildings table structure" - Tool Call: describe_table('wherobots_open_data', 'overture', 'buildings')

  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_knowledge_stats

  mcp-klever-vm

  Get summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for each type. Useful for understanding what knowledge is available before querying.

  Connector

• token_current_top_holders

  Nansen

  Get upto 25 (per page) top holders information for a specific token. **Note:** Using `labelType: smart_money` is not a good proxy for an overall market view. Use it only if user explicitly requests it, or to combine it with other non smart money data. **Modes:** - `onchain_tokens` (default): Analyze on-chain tokens by contract address - `perps`: Analyze Hyperliquid perpetual futures by symbol (chain auto-set to "hyperliquid") Columns returned (onchain_tokens mode): - **Address**: Wallet/contract address of the token holder - **Label**: Nansen label (e.g., exchange, whale, etc.) - **Balance**: Current balance held (numeric with K/M/B formatting) - **Balance USD**: USD value of token holdings (currency formatted) - **Ownership %**: Percentage of total token supply owned (percentage, 2 decimal places) - **Sent**: Total tokens sent from this address historically (numeric) - **Received**: Total tokens received by this address historically (numeric) - **24h Change**: Balance change in last 24 hours (numeric, can be negative) - **7d Change**: Balance change in last 7 days (numeric, can be negative) - **30d Change**: Balance change in last 30 days (numeric, can be negative) Columns returned (perps mode): - **Trader Address**: Address of the trader - **Trader Label**: Nansen label for the trader - **Side**: Position direction (Long/Short) - **Position Value USD**: Total USD value of the position (currency formatted) - **Position Size**: Size of the position in tokens (numeric) - **Leverage**: Leverage multiplier (e.g., "20X") - **Leverage Type**: Type of leverage (cross/isolated) - **Entry Price**: Average entry price (price formatted) - **Mark Price**: Current mark price (price formatted) - **Liquidation Price**: Liquidation price (price formatted) - **Funding USD**: Cumulative funding payments (currency formatted) - **Unrealized PnL USD**: Unrealized profit/loss (currency formatted) Sorting Options (default: amount desc): onchain_tokens mode: amount, valueUsd, total_outflow, total_inflow, balance_change_24h, balance_change_7d, balance_change_30d, ownership_percentage perps mode: position_size, position_value_usd, entry_price, leverage, upnl_usd, funding_usd, mark_price, liquidation_price Examples: # On-chain tokens (default mode) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "top_100_holders" } ``` # Hyperliquid perpetual futures ``` { "mode": "perps", "token_address": "PENGU", "label_type": "smart_money" } ``` # Find most active senders using filters ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "smart_money", "includeSmartMoneyLabels": ["All Time Smart Trader", "Fund"], "order_by": "total_outflow", "order_by_direction": "desc" } ``` # Find biggest accumulators (who received most tokens) ``` { "mode": "onchain_tokens", "chain": "ethereum", "token_address": "0xa0b86a33e6b6c4b3add000b44b3a1234567890ab", "label_type": "whale", "order_by": "total_inflow", "order_by_direction": "desc" } ``` # Perps mode with filters ``` { "mode": "perps", "token_address": "ETH", "label_type": "smart_money", "side": "Long", "upnlUsd": {"from": 10000}, "positionValueUsd": {"from": 100000}, "order_by": "position_value_usd", "order_by_direction": "desc" } ``` **Restrictions exclusively when querying for native tokens (ETH, BNB, etc.):** - Only supports sorting by `order_by='balance'` (others will fail) - With `label_type='top_100_holders'`: limited filters (balance, total_outflow, total_inflow, address, smart money labels) - For advanced filters, use different`label_type` or set `aggregate_by_entity=true` **orderBy Restrictions (use 'balance' to avoid API errors):** - Token address: 0xa0b86a33e6b6c4b3add000b44b3a1234567890ab **Does not** work for SOL in onchain_tokens mode (tokenAddress So11111111111111111111111111111111111111112). For SOL analysis, use perps mode instead.

  Connector

• ai_call

  Sats4AI - Bitcoin-Powered AI Tools

  When your task hits a wall that requires a human — booking, negotiating, navigating IVR menus, getting information from a business — send an AI voice agent to handle the call. The agent follows your instructions, has a real two-way conversation, auto-retries on voicemail (up to 3 attempts), and returns a full transcript with structured analysis. May return state='pending_confirm' with clarification questions if critical info is missing — call confirm_ai_call to proceed. Async — poll with check_job_status(jobType='ai-call'). ~150-250 sats for a 3-min US call. Languages: en-US, en-GB, es-ES, fr-FR, de-DE, ja-JP, zh-CN, multi. Pay with Bitcoin Lightning — no telecom account, no API key, no subscription. When NOT to use: not when you want to drive the conversation with your own LLM (use open_voice_bridge — you keep the brain, we provide PSTN/STT/TTS primitives). Not for one-shot TTS broadcasts or IVR delivery (use place_call). Not for SMS (use send_sms). Requires create_payment with toolName='ai_call', phoneNumber, and durationMinutes.

  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

• ioc_lookup

  ContrastAPI

  Enrich Indicator of Compromise (IP/domain/URL/hash) by auto-detecting type and querying abuse.ch feeds. Per-type source coverage: hash → ThreatFox only (Feodo and URLhaus do not index hashes); IP → ThreatFox + Feodo Tracker + URLhaus; domain / URL → ThreatFox + URLhaus. verdict.sources_queried lists what actually ran; verdict.sources_unavailable lists what failed (timeout / upstream error). Use as primary IOC triage tool when type unknown; use threat_intel for domain-only, hash_lookup for richer MalwareBazaar hash data. Free: 100/hr, Pro: 1000/hr. Returns {indicator, type, threat_level, sources, summary, verdict}.

  Connector

• shippingrates_lines

  ShippingRates MCP Server

  List all shipping lines in the ShippingRates database with per-country record counts. Use this to discover which carriers and countries have data before querying specific tools. Returns each carrier's name, slug, SCAC code, and a breakdown of available D&D tariff and local charge records per country. FREE — no payment required. Returns: Array of { line, slug, scac, countries: [{ code, name, dd_records, lc_records }] } Related tools: Use shippingrates_stats for aggregate totals, shippingrates_search for keyword-based discovery.

  Connector