Skip to main content
Glama
819,848 tools. Updated 2026-11-22 08:17

"A platform for trading stocks and financial securities" matching MCP tools:

  • 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. A verdict is always ABOUT A SPECIFIC SALE — `sale_analyzed` names it, and `buyer`/`seller` are the parties scored. If the response has `assessable: false` there is NO score and NO verdict: the name has no analyzable sale on record, or the lookup failed. Report that the name could not be assessed and say why. Do NOT describe it as clean, low-risk, or free of red flags, and do NOT describe unrun checks (funding, cluster, round-trip) as having come back negative.
    ConnectorNo auth
  • Get reference documentation for the Orderly Public Info API — a zero-auth single endpoint (POST /v1/public/query) for market, account, and platform data selected by a `type` field. Covers 24 query types (marketSummary, accountState, orderbook, candles, topAddresses, whaleContext, etc.); `queryType` accepts exact, partial, or fuzzy names and returns params, response fields, example, weight, and freshness; `category` lists a group (queryType wins if both are supplied); omit both for the overview and rate-limit rules. Read-only bundled docs — it does not call the endpoint. Use instead of get_api_info for zero-auth public data; use get_api_info for authenticated trading, get_indexer_api_info for historical analytics, and get_strategy_vault_api_info for vault data.
    ConnectorNo auth
  • Get the stocks whose daily price returns are most (or least) correlated with one stock — Pearson correlation of daily log returns on comparable raw closes (dividends excluded), computed over the trading days both stocks priced, never on raw price levels. Scope picks the candidate universe: Industry (default) ranks the subject's direct industry peers; Sector widens to sibling industries; Market ranges across the ~1,500 largest listed names and surfaces cross-industry relationships the classification misses (suppliers, commodity proxies). direction=Negative flips the ranking to the strongest inverse movers (hedge candidates). Candidates need a $100M market cap and enough overlapping trading days with the subject; each row reports the observation count behind its coefficient. Use GetStockPrices for the underlying series and the screener for fundamentals-based peer sets.
    ConnectorNo auth
  • Returns official financial disclosures from Congress and the OGE executive-branch feed. It defaults to Congress; branch selects Congress, executive, or both. Optionally filter by one stock or one official filer. WHEN TO USE: User asks what Congress, a senator, a representative, or an executive-branch official disclosed buying or selling. Examples: - "What stocks did Nancy Pelosi trade?" - "What did Donald Trump disclose trading?" - "Has any member of Congress bought NVDA?" - "Show me recent congressional purchases" PARAMETERS: - ticker_or_cusip or member: optional identity filter; provide at most one. member resolves only against the selected branch; ambiguous names return candidates - branch: congress (default), executive (OGE), or all official disclosures - direction: optional buy, sell, or other filter - filed_from / filed_to: optional inclusive disclosure-date range (YYYY-MM-DD); filed_from must be on or before filed_to - limit / cursor: page size and opaque continuation cursor; an explicit limit above the caller's tier fails rather than being changed WHEN NOT TO USE: - Use analyze_politician for one member's full profile + trading performance - Use analyze_stock for the synthesized smart-money verdict on a stock RETURNS: Cursor-paginated House, Senate, and/or OGE disclosures (selected by branch) with canonical ticker and CUSIP when verified, the ticker printed in the official disclosure as separate source evidence, filer, chamber, native transaction type, buy/sell/other direction, dollar range, dates, instrument details, and source link. An unresolved official ticker is returned as disclosed_ticker while ticker and security_cusip remain null. CITE: When you present these results, link `web_url` (the page with the full view) and cite record-level `source_url` filing or disclosure links when present.
    ConnectorNo auth
  • Get a Chinese-metaphysics signal on a binary prediction-market question (Polymarket/Kalshi style yes/no outcomes). Use when a user — or a trading agent — wants an UNCORRELATED, for-fun read on a market: 'will X happen by date Y'. Returns a lean (yes/no/neutral), a confidence, the 五行 reasoning from the resolution date's energy, and a mandatory disclaimer. This is ENTERTAINMENT and a falsifiable ritual — NOT financial advice. Always present it as a novelty signal, never as a recommendation to place a bet.
    ConnectorNo auth
  • Create a new ad group under a campaign. Every ad group belongs to one platform (body.platform, a platform id such as google-ads): only that platform receives it, its ads and its keywords. Leave it out on a campaign that runs on one platform; name it on a campaign that runs on several (400 AD_GROUP_PLATFORM_REQUIRED lists them). It is fixed once created — use copy_ad_group to run the same ads elsewhere. Returns the full updated/created object. Scoped to the active Space — see set_active_space to switch, or pass space_id to override for this one call.
    ConnectorAPI key

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides 11 composable MCP tools for A-share market research, covering quotes, news, technical signals, sector performance, portfolio risk, backtesting, and paper trading, with traceable data sources and calculation basis.
    MIT

Matching MCP Connectors

  • Taiwan stock picks, style comparisons, lookups, trading costs and plain-word idea backtests.

  • Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest.

  • One member of Congress: profile, aggregate trading stats (counts, volume range, average disclosure lag, most-traded tickers), the 20 most recent disclosed trades with links to the original government filing, the member's 5 most recent Periodic Transaction Reports, and the one sample scored trade the public page shows. Use it for 'what has this member been trading'. Get the member_id from search_members first. For more than 20 trades, page list_transactions with the same member_id. Returns a not-found error for an unknown id. Access: needs the agent token from a free Coldpine account, sent as 'Authorization: Bearer <token>'; without it the call returns setup steps instead of data. Read-only, cached for up to an hour.
    ConnectorNo auth
  • List and filter the CRM contacts (people who have written to or interacted with the connected accounts), each with `id`, `name`, `email`, `tags`, `subscribed` and `platform`, plus `count` with the total that matched before the limit. Use it to find a person or a segment; for one person's channels, custom fields and notes use get_contact, and for their messages list_conversations. Returns 40 by default and at most 200: if `count` is higher, narrow with tag, search, platform or accountId. The `id` is what get_contact, update_contact, set_contact_field and enroll_in_sequence take.
    ConnectorOAuth
  • [Trading Data API] ICT liquidity levels: buy-side liquidity (above swing highs) & sell-side (below swing lows), sweep/taken status, relative-equal pools, and nearest untaken targets. Crypto or stocks. **Example:** `/v1/liquidity-levels?symbol=TQQQ&timeframe=1h` Use when you want buy-side/sell-side liquidity levels and whether they were swept. Not for gap zones (use fvg) or actual liquidation events (use liquidations). Behavior: read-only. Priced via x402 (USDC on Base) or free with WICKEDAPI_API_KEY; with neither, you get HTTP 402 with the decoded price in payment_required (a price quote, not a failure).
    ConnectorNo auth
  • Analyze one stock, or check one chosen pair of stocks. One stock: HMM regime detection, Hurst exponent, Bollinger/Keltner squeeze, Monte Carlo forward simulation. A pair (`ticker` and `ticker_b`, e.g. KO and PEP): whether the two hold together for spread trading. The QuanterLab pairs check rates the evidence that the two prices hold together as strong, mixed or weak, with a score out of a hundred, from the Engle-Granger and Johansen cointegration tests, the spread's half-life, how much the hedge ratio moves, and how often the two stocks share a market regime. It is the check to run when someone asks "is X / Y a tradable pair?" about any two stocks; `start_pairs_scan` searches a whole index for pairs instead. Every account runs it within a daily allowance; a refused call does not count, and get_started and every run's answer give today's count. An analysis takes about 30 seconds to 2 minutes. The call returns `{task_id, status, kind, dashboard_url}`; `get_regime_analysis_progress` reports progress and, when it has finished, carries `result`: for one stock, the regime now and how long it has run, volatility against the stock's own history, how the stock behaves (trending, mean reverting or a random walk), its trend and its drops, rounded; for a pair, how strong the evidence is that the two hold together and the check's score, the cointegration tests as p-value bands, the spread's half-life, the hedge ratio's variation, the correlation, and how often the two shared a regime, rounded. Unlike `start_regime_optimization`, which uses HMM regimes to grid-search trading thresholds, this analysis is descriptive. Args: ticker: Stock symbol (uppercased). Required. ticker_b: Optional second ticker; with it the analysis checks the pair (`ticker` / `ticker_b`) for spread trading. mode: Optional. `'volatility'` runs only the squeeze module. years: Lookback window in years (default 2). params: Optional dict overriding module-specific knobs. Most useful: `hmm_enabled` / `hurst_enabled` / `squeeze_enabled` / `mc_enabled` (disable modules); `hmm_states`; `mc_simulations`. question: Optional. One sentence restating what the run should answer, not the person's message: the title of the report the finished run becomes, and kept only as that. When the run has finished, its progress answer also carries `report_url`: the analysis written up as a QuanterLab report (the market states and their spells, or for a pair the checks of whether the two hold together). The call waits for the run while it is likely to finish inside it; the run's card in the chat shows the result or, for a longer run, how far it is, and fills in by itself, with the next steps as choices and the report link. A run started here needs no `show_report_card`.
    ConnectorOAuth
  • Get reference documentation for the Orderly Indexer API, a read-only source of historical and aggregated trading data: volume and fee metrics, account events, trades, and rankings. Omit both parameters for an overview with base URLs, categories, common errors, and usage tips; pass `category` to discover all endpoints in an area, or `endpoint` to fuzzy-match one endpoint and return its parameters, request/response schemas, and TypeScript example (category takes precedence if both are supplied). Bundled docs lookup only — no API call, credentials, or rate limits. Use for analytics, dashboards, account history, and leaderboards; for live trading operations use get_api_info, and for zero-auth market data use get_public_info_api_info.
    ConnectorNo auth
  • Use this when the user wants the numbers for their posts: "how are my clips doing", "which TikTok took off", "how many views did my Short get", "show my scheduled posts". Returns per post the platform, status, post URL, caption, clip title, the latest views, likes, comments, shares and saves the platform sent (null = the platform sends no such count) and views at 1 hour, 24 hours and 7 days. platform: tiktok, youtube, instagram, ... or all (default). status filters draft, scheduled, posted or failed (empty = all; status "draft" lists the post_id that update_draft and delete_draft take). limit 1-50, newest first. Covers posts RipClip published or planned. Not for: a recap of the week (weekly_report), platform against platform (compare_platforms), what is growing fast (whats_taking_off) or follower counts (get_account_stats). Free and read only.
    ConnectorNo auth
  • Check whether Tradetron supports trading a given underlying. Deterministic lookup against the bundled underlying catalog (snapshot of TT's `underlying` table). Use this BEFORE answering any "can I trade X?" / "is X tradable?" / "is X listed?" question — it is authoritative. Do NOT guess from training data; if a symbol is not in this catalog, Tradetron does not support trading it. Matching is case-insensitive and alias-aware: 'nifty' / 'NIFTY 50' / 'Nifty50' all collapse to the same canonical symbol; 'BANKNIFTY' resolves to 'NIFTY BANK'. Returns: supported: True if at least one match exists. resolved_to: canonical symbol when the input was an alias. matches: [{symbol, exchanges, instrument_types, lot_sizes, kinds, emitter_buildable}]. `kinds` is the field that tells a CASH equity from a derivative — an equity typed OPTSTK is not an option, and nothing else in the response says so. `emitter_buildable` (also at top level) says whether the builder can author a leg on it. Both were returned undocumented. message: one-liner safe to relay to the user. may_be_a_name: true when the query looks like a company or index NAME rather than a ticker — do not report it as unsupported. symbol_candidates: on a miss, symbols whose company/index NAME matches the query ("Reliance Industries" → RELIANCE) — re-check the intended one by symbol. synthesis_instructions: guidance for you, not text for the user. For listing all underlyings (e.g. "what stocks are on Tradetron?" or "which index options can I trade?") use tt_list_underlyings.
    ConnectorOAuth
  • Is a stock exchange open for trading right now (or at a given time)? Returns { open: true/false } plus status, when it next opens (weekends and holidays are skipped), and when it closes if currently open. The fastest answer to "is <exchange> open?".
    ConnectorNo auth
  • Lines up 2 to 5 U.S.-listed stocks or ETFs side by side on Market Eyes Live MELANY ratings: conviction tier (weakest to strongest: Unfavorable, Hold, Favorable, Highest Conviction), 0 to 100 composite score, and the valuation, quality and momentum factor scores. Use this when the user wants several tickers' ratings shown together, for example 'compare AAPL, MSFT and GOOGL on quality and valuation' or 'NVDA vs AMD ratings'. Do not use for real-time quotes, price history, options, crypto, futures, non-U.S. listings, or a personal recommendation. Limitations: draws only on the daily-refreshed rated set; a ticker outside it returns a note instead of scores (get_stock_rating can score a covered ticker live), and a ticker outside U.S.-listed stocks and ETFs returns a not-covered note; it does not return any trade plan values (has_trade_plan marks a ticker for which Market Eyes Live has a trade plan; the plan values are part of a Market Eyes Live subscription). Methodology and the graded public record: https://marketeyeslive.com/how-melany-is-tested.html. Research data, not financial advice; this tool is read-only and never places trades.
    ConnectorNo auth
  • Calculate the cash ratio: cash and marketable securities divided by current liabilities — the most conservative liquidity measure. Formula: Cash Ratio = (Cash + Marketable Securities) / Current Liabilities. WHEN TO USE: Use for the strictest view of liquidity, or when a company is in distress and only cash-like assets can be relied on. WHEN NOT TO USE: Do NOT use in isolation for healthy operating businesses — it ignores receivables and inventory that normally convert to cash. BEHAVIOUR: pure deterministic calculation — no side effects, no network or storage access; idempotent and non-destructive; identical inputs always produce identical outputs. Division by zero or non-finite inputs returns an explicit error instead of a number. RETURNS: JSON object { cash_ratio: number (e.g. 0.5 = 0.5x), inputs }. PARAMETERS: cash_and_equivalents (required): Cash and cash equivalents, e.g. 80000. Must be >= 0. marketable_securities (required): Short-term marketable securities, e.g. 30000. Must be >= 0. current_liabilities (required): Total current liabilities, e.g. 220000. Must be > 0.
    ConnectorNo auth
  • Per-post metrics for posts published inside the window, sorted by a metric or by publish date, paginated. Use it for "top posts", "which post got the most comments" and "how did post X do". Covers posts published through AdaptlyPost and posts discovered on the connected accounts; Google Business Profile posts are listed with null metrics, since that platform reports only location impressions; discovered posts have postId and postPlatformId set to null, while AdaptlyPost posts carry the postId used by get_post. Returns { posts, total, page, limit, hasMore }; each post has platform, publishedAt, title, thumbnailUrl, permalink, connectionId, accountName and metrics { views, likes, comments, shares, saves, clicks, impressions, reach, engagementRate, plus engagedViews, averageViewDurationSeconds and averageViewPercentage on YouTube }, with null for metrics the platform does not report. Sort by a metric for a ranked list (list_top_posts returns the top few in one call); PUBLISHED_AT (default) for a chronological review. Not for publishing status: use list_post_results for that.
    ConnectorOAuth
  • Add a new note to a trading day — any day, traded or not; `date` is YYYY-MM-DD in the journal timezone. Days hold any number of notes, so this never overwrites: to change an existing note use journal_update_note, and for a note about one specific trade use journal_update_trade's `notes`. Returns the note with its id. Day notes in the LuxAlgo journal: https://docs.luxalgo.com/platform/workspaces/journal/notes Requires signing in with a LuxAlgo account (OAuth).
    ConnectorNo auth
  • Link an algorithm to a trading instance with capital allocation and start live trading. algo_id is the saved algo id (from create_algo / list_my_algos), not LinkedAlgo id. instance_id is from create_instance / list_instances. ALWAYS ask the user for capital_allocation — never invent a dollar amount. Capital is from broker buying power; the cumulative sum across this agent's live algos (allocated AI Trading Power) must stay ≤ policy max_total_capital. First call with confirm_allocation=false; server returns allocation_requires_confirm with broker_equity, allocation_pct_of_equity, and warning_level (high≥50%, critical≥90%). Show those to the user with risk settings; after explicit OK retry with confirm_allocation=true (acknowledge_capital_risk still accepted as alias). capital > equity is hard-blocked. Optional risk_preset override: conservative|moderate|aggressive|custom. On success check engine_started (or utml_started), is_live, symbols, timeframe, and capital vs equity.
    Connector
    Destructive
    OAuth
  • Delete a post from iHatePosting. ONE SEND AT A TIME: a SCHEDULED post going to several accounts is stored as one post PER SEND, so deleting one cancels only that platform and leaves the rest scheduled — pass the `postId` that create_post returned on that particular send, or the id of the row list_posts shows for it. There is no need to cancel a whole multi-platform post to drop one platform from it. A DRAFT IS DIFFERENT: until it is scheduled, a draft is ONE post holding every platform it is aimed at (all its sends share one postId), so deleting it removes every platform — to drop one platform from a draft, use update_post with the remaining accountIds instead. The reply's `platformsRemoved` names every platform the delete took; for one send of a group, `stillScheduled` lists the sends still going out and `otherSends` the rest of the group (already published or failed), each with its status; their `scheduledAt` is UTC (it ends in Z) and `scheduledLocal` is the same moment in the account owner's timezone — report that one. THIS DOES NOT UNPUBLISH ANYTHING: a post that has already gone out stays live on the network, and deleting it here only removes iHatePosting's record of it. For that reason a published post is refused unless you pass force: true, and you should only do that after telling the user in words that the platform post will remain. A post that is publishing at this moment is never deletable, forced or not — the worker is mid-flight on it. Deleting a scheduled post stops it going out.
    Connector
    Destructive
    No auth
  • Aggregate performance for one connected channel, or for every channel at once. Returns impressions, reach, likes, comments and engagement rate for the period, the change against the preceding period of the same length, and the follower series. Omit `platform` for a team-wide total; pass `platform` (plus `channelName` or `providerId` from list_connected_accounts when that platform has more than one account connected) to scope it. `providerId` still identifies the account after its handle changes. `period` is 7d, 30d, 90d or all, defaulting to 30d. Use this for "how did LinkedIn do this month?"; use get_post_metrics for a single post and get_best_time_to_post for scheduling.
    ConnectorAPI key