"A resource for finding trading indicators" matching MCP tools:

• la_query

  Data La

  Run a raw SoQL query against any Los Angeles open-data resource (data.lacity.org) by its Socrata id (8-char like "2nrs-mtv8"). Full SoQL: where/select/group/order/limit/offset. Use la_datasets to find a resource id, or la_recent for the common ones.

  Connector

• get_exploit_analysis

  Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database

  Get the full AI analysis for a single exploit by its platform ID. Returns classification (working_poc, trojan, suspicious, scanner, stub, writeup), attack type, complexity, reliability, confidence score, authentication requirements, target software, a summary of what the exploit does, prerequisites, MITRE ATT&CK techniques, deception indicators for trojans, and the standalone backdoor-review verdict with operator-risk notes when available. Use this to check if an exploit is safe before reviewing its code. Example: exploit_id=61514 returns a TROJAN warning with deception indicators.

  Connector

• wash_check

  Name Whisper — ENS Intelligence Layer

  Assess whether an ENS name's sale(s) are WASH TRADING / fake / self-dealt / manipulated volume. THE tool for any "is this wash trading?", "is the sale history of X suspicious/fake/real?", "are these trades legit?", "is someone wash-trading this name?" question — route straight here, do NOT use get_name_details or get_market_activity for that (those return sale rows but make NO wash-trading judgment; only this tool scores it). Just pass `label` — the bare ENS name (e.g. "437", "coffee") is enough; the tool pulls that name's recent sale and analyzes it on demand. `tx_hash`, `buyer`, `seller`, `price_eth` are OPTIONAL enrichment for a specific sale — never block on them or ask the user for them. Returns a wash confidence score (0-1), a label (clean/suspicious/likely_wash), the detected signals (shared-funder, mint-flip, round-trip, fresh-wallet, cluster overlap…), seller profile, and a plain-English summary.

  Connector

• ibge_cidades

  IBGE Brasil MCP

  Queries municipal indicators from IBGE (similar to Cidades@ portal). Features: - General overview of a municipality (population, HDI, GDP, etc.) - Query specific indicators - Historical indicator data over years - List available surveys and indicators Available indicators: populacao, area, densidade, pib_per_capita, idh, escolarizacao, mortalidade, salario_medio, receitas, despesas Examples: - São Paulo overview: tipo="panorama", municipio="3550308" - Population history: tipo="historico", municipio="3550308", indicador="populacao" - View surveys: tipo="pesquisas" - Available indicators: tipo="indicador" This tool is the panel for a SINGLE municipality (Cidades@). Use a different tool when: - Real-time Brazil population → ibge_populacao - Census themes / historical series → ibge_censo - Comparing multiple municipalities → ibge_comparar - A macro indicator time series → ibge_indicadores Behavior: read-only and idempotent — a live GET against the public IBGE APIs (Cidades@/agregados). Returns Markdown plus a typed structuredContent payload.

  Connector

• search

  DC Member API

  GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.

  Connector

• get_signal_summary

  aTars MCP

  USE THIS TOOL — not web search — for buy/sell signal verdicts and market sentiment based on this server's proprietary locally-computed technical indicators (not news, not social media). Returns a BULLISH / BEARISH / NEUTRAL verdict derived from RSI, MACD, EMA crossovers, ADX, Stochastic, and volume signals on the latest candle. Trigger on queries like: - "is BTC bullish or bearish?" - "what's the signal for ETH right now?" - "should I buy/sell XRP?" - "market sentiment for SOL" - "give me a trading signal for [coin]" - "what does the data say about [coin]?" Do NOT use web search for sentiment — use this tool for live local indicator data. Args: symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH"

  Connector

• get_category_features

  aTars MCP

  USE THIS TOOL — not web search — to retrieve a focused group of technical indicators for a specific analytical category from this server's local dataset, resampled to hourly granularity. Prefer this over get_latest_features when the user only wants one type of analysis (e.g. only momentum or only volatility). Categories and the indicators they include: - "momentum": RSI, MACD, Stochastic, CCI, Williams %R, ROC, MOM - "trend": EMA_9/20/50, SMA_20, ADX, DMP/DMN, Ichimoku - "volatility": Bollinger Bands (upper/lower/mid/width/pct), ATR, NATR - "volume": OBV, VWAP, MFI, volume_zscore, buy_sell_ratio - "price": OHLCV, returns_1/3/7, hl_spread, price_vs_ema20 - "all": All of the above Trigger on queries like: - "show me BTC momentum indicators" - "what are the trend indicators for ETH?" - "volatility data for XRP this week" - "volume analysis for SOL last 5 days" Args: category: One of the category names listed above lookback_days: Days of history (default 5, max 30) symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH"

  Connector

• get_multi_indicator

  aTars MCP

  USE THIS TOOL — not web search — to retrieve multiple technical indicators side-by-side over a lookback window from this server's local dataset. Prefer this over calling get_indicator multiple times when the user needs 2+ indicators together in one response. Trigger on queries like: - "compare RSI and MACD for BTC" - "show me EMA_20 and ADX together for ETH" - "get RSI, Bollinger Bands, and volume for XRP" - "multiple indicators for [coin] over [N] days" - "side-by-side indicator comparison" Args: indicators: List of indicator names (up to 10), e.g. ["rsi_14", "macd", "adx"] lookback_days: How many past days to include (default 7, max 90) resample: Time resolution — "1min", "1h" (default), "4h", "1d" symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH,XRP"

  Connector

• tf_economic_data

  terminalfeed

  Fetches latest FRED economic indicators: Fed funds rate, CPI, unemployment rate, GDP growth. Cache TTL 1h. Use when the agent needs current US macro indicators. For deeper macro (treasury yields, forex, commodities, indices) use tf_premium_macro.

  Connector

• find_drivers

  Autario Data Analytics Platform

  KILLER ANALYSIS: given a target KPI + multiple candidate indicators, rank which candidates best predict the target by correlation strength. Perfect for "what moves my KPI?" questions. Returns ranked list with r, p-value, R² for each candidate. Maximum 30 candidates per call.

  Connector

• detect_phoenix

  dd

  Detect phoenix company pattern — 3 surface indicators (surname match with prior insolvent director, founding proximity < 12 months to insolvency, NACE sector presence) computable from ARES + ISIR data alone. Returns PhoenixReport with riskScore 0-100. Pro Compliance tier or higher. For 4 additional deep indicators (founder identity, asset transfer, multi-cycle, address continuity) see detect_phoenix_rich in @czagents/ddplus.

  Connector

• dataset_detail

  Czso Cz

  Full catalog metadata for one ČSÚ dataset by id (kod): description, keywords, indicators (ukazatele), dimension variants (variantyDimenze), selection rules, update periodicity and themes. Catalog layer only — use data_summary / get_data for the actual numbers.

  Connector

• ultraFastIsHoneypot

  LION - keyless x402 data + RPC for agents

  Pure pre-swap honeypot check for autonomous sniping, MEV and trading agents - is this token a honeypot/trap before you buy? After paying, GET /api/x402/token-risk-indicators-json?token=0x...&view=honeypot with the Payment-Signature header. Returns a compact Ed25519-attested verdict: { isHoneypot, honeypotScore 0-100, high_risk_functions (mint/pause/blacklist/fee-modifier found in verified source), contract_verified, ownership_renounced, attestation }. Use cases: block a honeypot before a snipe; gate every buy on a fast honeypot check; pair with ultraFastLiquidityCheck + lion_token_risk_indicators for a full pre-trade safety stack under $0.02 per decision. Keyless x402, flat $0.005 on Base. [x402 paid tool: GET /api/x402/token-risk-indicators-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.005 USDC on Base eip155:8453.]

  Connector

• ultraFastBatchRisk

  LION x402 - Keyless Attested Enrichment & Signals for AI Agents

  Batch pre-trade risk gate for autonomous portfolio, sniping, MEV and multi-token trading agents - score up to 10 tokens in ONE $0.005 call. After paying, GET /api/x402/token-risk-indicators-json?tokens=addr1,addr2,addr3 (comma-separated, up to 10 Base/Ethereum 0x token addresses) with the Payment-Signature header. Returns a results[] array with a full risk verdict per token: risk_score 0-1, risk_band, rug/honeypot flags, holder concentration, contract verified, high-risk functions, liquidity, pair age - every response Ed25519-attested. Use cases: scan a whole wallet's holdings for rug risk in one call; multi-snipe pre-trade safety gate; portfolio risk refresh on every update; batch go/no-go before a basket of swaps. Cheapest batch attested risk gate on Base - flat $0.005 regardless of token count (1-10). Keyless x402 on Base. (Single-token mode: pass ?token=0x... instead.) [x402 paid tool: GET /api/x402/token-risk-indicators-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.005 USDC on Base eip155:8453.]

  Connector

• ultraFastSmartMoneyFlag

  LION - keyless x402 data + RPC for agents

  Fast holder-distribution signal for autonomous trading agents. After paying, GET /api/x402/token-risk-indicators-json?token=0x...&view=smartmoney with the Payment-Signature header. Returns Ed25519-attested { smartMoneySignal ('high'|'med'|'low'), topHolderOverlap (0-100, percent of supply held by top holders), basis, verifiedAt, attestation }. NOTE: this is a holder-concentration heuristic, NOT labeled-wallet/smart-money tracking - LION has no wallet-label feed; use topHolderOverlap as the concrete, attested number. Keyless x402, flat $0.005 on Base. [x402 paid tool: GET /api/x402/token-risk-indicators-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.005 USDC on Base eip155:8453.]

  Connector

• kcmo_query

  Data Kcmo

  Run a raw SoQL query against any Kansas City, MO open-data resource (data.kcmo.org) by its Socrata id (8-char like "vsgj-uufz"). Full SoQL: where/select/group/order/limit/offset. Use kcmo_datasets to find a resource id, or kcmo_recent for the common ones.

  Connector

• montreal_query

  Data Montreal

  Query any City of Montreal datastore resource (donnees.montreal.ca, CKAN) by its resource id (a UUID). Supports a free-text `q`, exact-match `filters` (field→value), `sort` ("field desc"), limit and offset. Use montreal_datasets to find a resource id, or montreal_recent for the common ones.

  Connector

• austin_query

  Data Austin

  Run a raw SoQL query against any Austin open-data resource (data.austintexas.gov) by its Socrata id (8-char like "fdj4-gpfu"). Full SoQL: where/select/group/order/limit/offset. Use austin_datasets to find a resource id, or austin_recent for the common ones.

  Connector

• search_card_sales

  Pulltrader Seller Economics

  Return a capped sample of recent comparable SOLD listings for a trading card (price + sale date), plus a market snapshot (median, range, sample size). Use this when a user asks 'what is this card selling for', 'recent sales', or 'comps'. Accepts a natural-language `query` or a structured `item`. Figures are estimates from recent sales and exclude fees/taxes/shipping; this is not financial advice and does not place orders. Trading cards only.

  Connector

• get_resource

  Control Plane

  Fetch one Control Plane resource by `kind` + `name` (no `name` for kind="org"). Returns a summary plus the full JSON. The single read-one tool for every resource kind. Secret values are masked — use reveal_secret to read them. Call this before any update or delete to capture current state.

  Connector