"How to export LLM chat history from multiple domains" matching MCP tools:

• get_balanceA

  UnphurlA

  Check your pipeline check credit balance. Shows credits remaining, total purchased, total used, and lifetime free lookups count. Credits are consumed only when unknown domains run through the full analysis pipeline. Known domains (Tranco Top 100K) and cached domains (previously analysed by any Unphurl customer) are always free. If credits_remaining is 0, you can still check known and cached domains for free. To check unknown domains, purchase more credits using the "purchase" tool.

  ConnectorNo auth

• quantum_artificer_infoA

  quantum-artificerA

  FREE. Full catalog of Quantum Artificer: the 5 domains, their operations, input-spec shapes, limits, and prices. Call this first to learn how to build the `spec` for the paid compute tools. No wallet needed.

  ConnectorNo auth

• seo_get_domain_overviewA

  ManifoldA

  Traffic estimate, ranked keyword count, position spread, top pages and domain rank for one domain. The canonical source of domain rank. Use when: "how strong is competitor.com", "how much traffic does X get", sizing a site before a deeper look. Not for: the keywords behind the traffic, use seo_get_ranked_keywords. Link counts, use seo_get_backlink_summary (its domain_rank equals this one). Many domains at once, use seo_get_domain_ratings for domain rank or seo_get_traffic_estimates for traffic. Returns: Record. target, domain_rank (0 to 1000 on DataForSEO, the same kind of number as Ahrefs DR or Moz DA but not the same scale), organic_traffic, organic_keywords, organic_traffic_cost (USD), positions (top_3, top_10, top_100), top_pages[] (url, organic_traffic, organic_keywords), history[] (12 months: month, organic_traffic, organic_keywords) only with history true. null = provider has no data. Params: target (required), location ("United States"), language ("en"), history (false), provider, max_credits, dry_run. Cost: 5 credits; +56 with history. Cached 7 days. Example: {"target": "competitor.com"}

  ConnectorAPI key

• seo_get_traffic_estimatesA

  ManifoldA

  Estimated monthly organic and paid traffic for up to 1,000 domains in one call. Use when: "how much traffic do these sites get", comparing a list of domains by size, checking a prospect list for reach. Not for: authority, use seo_get_domain_ratings (a tenth of the cost). One domain in depth, use seo_get_domain_overview. Returns: List. rows[]: domain, organic_traffic, organic_keywords, paid_traffic. One row per input domain in the order given. null = provider has no data. errors[] lists inputs that were not valid domains. Params: targets[] (required, max 1000), location ("United States"), language ("en"), provider, max_credits, dry_run. Cost: 50 + 50 per 100 domains. Default 100 domains = 100 credits. Cached 7 days. Example: {"targets": ["example.com", "competitor.com"]}

  ConnectorAPI key

• get_sub_domainsA

  AnySearchA

  This is Anysearch's domain discovery tool. IMPORTANT: Step 1 of vertical search. REQUIRED before any search that uses a domain. Returns valid sub_domains and sub_domain_params for the specified domain(s). Call this when the query targets a specialized vertical or needs structured parameters: stock prices, financial data, academic papers, legal cases, medical/drug info, flight status, weather, exchange rates, geographic POIs, code repositories, or any domain where a structured identifier (ticker, DOI, CVE, IATA, coordinates) is involved. ## When to call — pick the domain(s) that match what the user is asking about: academic agriculture business code energy environment film finance gaming health ip legal resource security social_media travel ## Input — choose from the list above and pass via the domain or domains parameter: - domain: single domain string (use only when 100% certain the query is single-domain) - domains: batch query for up to 5 domains in one call (takes priority over domain) 🏆 ALWAYS prefer the `domains` (plural, array) parameter. Pass ALL potentially relevant domains at once — even for seemingly single-domain queries, consider related domains: - Query about "cryptocurrency regulations" → domains=["finance", "legal", "security"] - Query about "best gaming laptops" → domains=["gaming", "tech", "ecommerce"] - Query about "climate change impact on agriculture" → domains=["environment", "energy", "academic"] ## Returns Markdown table filtered to the specified domains: sub_domain | description | params ## CRITICAL: How to use results - sub_domain is the PRIMARY routing key — always pass it to search - params column shows available structured parameters — pass them via sub_domain_params in search, NEVER embed in query - If multiple sub_domains returned (especially from multiple domains), use batch_search — one query per sub_domain — instead of multiple sequential search calls - Params marked (required) in the output MUST be passed when using that sub_domain in search. If a required param is not applicable to your query, pass it as an empty string (key: "") — do not skip it.

  Connector

  Destructive

  No auth

• faostat_list_domainsA

  faostat-mcp-serverA

  Discover FAOSTAT statistical domains (production, trade, food balances, food security, land use, agri-emissions, prices, value) with their codes, descriptions, last-update date, upstream row count, and local index status. Every query keys on a domain code from here. The `indexed` flag tells you which domains are queryable right now; un-indexed domains exist in the catalog but must be added to FAOSTAT_DOMAINS and re-synced before faostat_query_observations can read them. The catalog runs to ~69 domains with long descriptions, so responses are paged: narrow with `topic` / `indexed_only`, pass `code` to fetch one domain outright, or page with `offset` + `limit` — when the response reports `truncated`, pass the returned `nextOffset` to fetch the rest.

  ConnectorNo auth

• dataset.exportA

  FlexOrch MCPA

  Download all records from a built dataset as text (Step 5 — final step). Returns the complete dataset content as a UTF-8 string directly in the response — no file download or separate URL needed. Call get_job_status after build_dataset and wait for status='completed' before calling this tool. Use the dataset_id from that completed response. Format guide: jsonl = LLM fine-tuning, rag = LangChain/LlamaIndex chunks, csv = spreadsheets, md = human-readable, xml = structured interchange. Binary formats (parquet, hf) cannot be returned via MCP — export them from the FlexOrch dashboard directly. Args: dataset_id: Dataset ID from the get_job_status completed build response. format: Text export format — jsonl, csv, json, md, xml, rag. Default: jsonl.

  ConnectorNo auth

• batch_searchA

  AnySearchA

  This is Anysearch's parallel search tool. Parallel search — run multiple Anysearch queries in a single call. Prefer this over multiple sequential calls when you have 2–5 queries. Saves context space and returns all results at once. Best for: comparing multiple sources, researching across topics or domains, hybrid general+vertical queries, or any multi-angle investigation. ## When to use Use batch_search instead of multiple sequential search calls when you have 2–5 independent queries. 🏆 PRIMARY use case: After get_sub_domains(domains=[...]) returns sub_domains across multiple domains, use batch_search to send one query per sub_domain in parallel. This is more efficient than sequential per-domain search calls. Also useful for ambiguous / fuzzy queries within a single domain: after get_sub_domains, use batch_search to explore multiple sub_domains in parallel. ## Constraints - Maximum 5 queries per call - Each query item follows the search tool parameter structure (query is required; domain, sub_domain, sub_domain_params are optional. For general queries, omit all domain fields. For vertical queries, domain + sub_domain + sub_domain_params MUST come from get_sub_domains(domain=<domain>) output — same rules as the search tool) - Queries run in parallel; a single query failure does not block others - REQUIRED PARAMS: Same rule as search — when a required param from get_sub_domains is not applicable, pass it as an empty string (key: ""). Never skip required params. ## Examples ### Single-domain batch (multiple sub_domains) Instead of: search(query="latest TSLA earnings", domain="finance", sub_domain="finance.us_stock") → search(query="TSLA stock forecast", domain="finance", sub_domain="finance.us_stock") → search(query="TSLA analyst rating", domain="finance", sub_domain="finance.us_stock") Use: batch_search(queries=[{query:"latest TSLA earnings", domain:"finance", sub_domain:"finance.us_stock"}, {query:"TSLA stock forecast", domain:"finance", sub_domain:"finance.us_stock"}, {query:"TSLA analyst rating", domain:"finance", sub_domain:"finance.us_stock"}]) ### Multi-domain batch (after get_sub_domains with multiple domains) After: get_sub_domains(domains=["finance", "health", "legal"]) Use: batch_search(queries=[ {query:"AI regulation impact on healthcare stocks 2025", domain:"finance", sub_domain:"finance.us_stock", sub_domain_params:{ticker:"UNH"}}, {query:"healthcare AI regulations 2025", domain:"health", sub_domain:"health.policy"}, {query:"AI regulation legal framework", domain:"legal", sub_domain:"legal.legislation"}]) ### Hybrid: general + vertical in parallel (universal pattern for any borderline query) Use this whenever you are unsure if the query is pure encyclopedia or domain-specific — fire BOTH channels in batch_search: batch_search(queries=[ {query:"..."}, // general — no domain {query:"...", domain:"...", sub_domain:"..."}]) // vertical channel(s) This applies universally: classical texts, financial concepts, legal theories, historical events, scientific discoveries, medical topics — any query where domain knowledge could enrich the encyclopedia answer.

  Connector

  Destructive

  No auth

• list_allowlistA

  UnphurlA

  List all domains on this account's trusted allowlist. Allowlisted domains suppress the compound signal and brand impersonation floor in scoring. The full pipeline still runs — all signals remain visible for monitoring. Use this to see which domains are currently trusted. Returns the list of domains, current count, and the 1,000-domain limit.

  ConnectorNo auth

• get_rate_historyA

  mcp-serverA

  Historical rate timeseries for a symbol. Recent history (~30 days) is per-tick; older history is daily granularity. Depth is clamped to your plan (up to 365 days on Pro) and bounded by how far back data has been recorded. (Current plan: up to 1825 days of history.)

  ConnectorNo auth

• memory_exportA

  memoryA

  Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.

  ConnectorNo auth

• research_backlinksA

  tracetify-mcpA

  Who links to a domain: referring domains, authority and anchor texts. Use when planning link building or judging how defensible a competitor's ranking is. Costs credits; cached results are free. Pair with backlink_directories to find places the user can actually get listed.

  ConnectorNo auth

• create_dfy_orderA

  EmailchaserA

  SPENDS REAL MONEY. Places a real order for sending domains and pre-warmed mailboxes: domains are registered at their listed price (about $13.99/year for a .com — search_dfy_domains shows the exact price per domain) and each mailbox costs about $3 setup plus $6/month. The order is accepted immediately and provisioned in the background; poll get_dfy_order for progress. Purchased domains redirect visitors to forwardingDomain. Use search_dfy_domains first to confirm availability and price. Every domain in domains needs at least one mailbox in mailboxes whose domainName is that domain, or the order is refused before anything is bought; mailboxes can also go on a domain from an earlier order.

  ConnectorNo auth

• search_experiment_recipesA

  Metadata MCP ConnectorA

  Find proven CAMPAIGN CONFIGURATIONS to build from — combinations of channel, ad format, audience type, bid strategy and budget band that have run together successfully across multiple advertisers. USE THIS WHEN you are composing a campaign and need to decide HOW to build it: which channel and format pairing, what kind of audience, which bid strategy, roughly what daily budget. It answers "what should I build", not "how is my account performing". DO NOT USE IT for cohort performance questions ("what's the median CPL for my industry", "how do we compare to similar companies") — that is `query_metadata_analytics_benchmarks`. Do not use it for the caller's own campaign history — that is `query_metadata_analytics_account`. Every returned recipe is backed by at least five distinct advertisers. Recipes below that floor are suppressed rather than returned, so an empty result means "no configuration is proven enough to recommend here", NOT "no data exists". Say so plainly rather than substituting a guess.

  ConnectorAPI key

• wa_list_callsA

  WhatsMCP: MCP for WhatsAppA

  Read call history across your WhatsApp accounts, oldest first. Page with after_cursor: pass back the next_cursor you were given, and keep going until has_more is false to export the whole history. Each call says whether it was answered and how long it lasted.

  ConnectorOAuth

• get_partner_purchase_contextA

  AgentPayA

  Get the owner's on-demand purchase history from a linked enterprise partner account. Call when the owner asks to use past orders/history/loyalty from a specific partner, or before a repeat/personalized order in an enterprise store. Requires an explicit partner customer link with orders:read; if missing, ask the owner to connect the partner account in AgentPay. Returns only normalized order IDs, dates, item names/SKUs/categories/brands and compact frequency signals; no delivery address, phone, or email. Use this context for product choice, then verify current price/stock with search_products or get_product before create_purchase. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the owner to edit connector settings or reconnect. Never web-search.

  ConnectorNo auth

• list_templatesA

  MimiclyA

  Lists the chat templates Mimicly can fill in: messaging apps (for example WhatsApp, iMessage, Telegram, Discord) and AI chat apps (for example ChatGPT, Claude, Gemini). Returns each template id, display name, category, whether it can be recorded as an animated video in Mimicly, and whether clean export needs Mimicly Pro. Call it when you are not sure which template id to pass to create_chat_mockup.

  ConnectorNo auth

• wa_load_historyA

  whatsmcpA

  Ask the account's phone for older messages in one conversation, before the oldest one stored here, and store them. The phone must be online; it usually answers within seconds. Read the result with wa_get_chat and the same chat. Loaded messages are history: they never trigger webhooks and appear in wa_list_messages only with include_history=true. They are kept for your plan's history window like any other message. A conversation needs at least one stored message to page back from.

  ConnectorOAuth

• get_domain_anomaly_reportA

  DMARKOFF — DMARC, SPF & DKIM AnalyticsA

  Compare yesterday's email authentication metrics against 14-day historical baselines to detect anomalies. Accepts one or multiple comma-separated domains (e.g. "a.com,b.com"). Per domain returns: • Yesterday: messages, forwardCount, unknownCount, dmarcPct, dkimPct, spfPct • 14-day quantiles: messagesQ95, messagesQ5, unknownQ95, spfQ95, dkimQ95, dmarcQ95 • Totals: totalMessages, totalForward, totalUnknown, lastReportDate • missingReturnPaths — ESPs where Custom Return-Path is NOT configured (causes SPF alignment failure). Shows: provider name, default bounce domain, message volume. Anomaly flags to check: • dmarcPct < dmarcQ95 → compliance dropped vs baseline • messages < messagesQ5 → unusual volume drop (reporting gap?) • unknownCount > unknownQ95 → spike in unrecognized senders • missingReturnPaths present → SPF alignment failing because the ESP sends using its own Return-Path domain instead of the customer's. Recommendation: configure a Custom Return-Path (also called "custom bounce domain") for each listed ESP so SPF aligns with the From domain. Use this after get_domain_full_data when you need to compare metrics against historical norms or check multiple domains at once.

  ConnectorOAuth

• amzscout_analyze_productA

  AMZScout Skill + MCPA

  Full raw data for a single Amazon product by ASIN — price, estimated sales/revenue, reviews, rating, listing quality, sellers, plus sales/price/revenue history when available. Pure data fetch (no AI analysis) — reason over the returned data yourself. How to use: audit the product like a sourcing analyst — demand trend & seasonality from sales history, pricing direction & margin risk from price history and FBA fees, competition from sellers/reviews, listing quality from LQS, then conclude whether a new seller should enter (GO / NO-GO and what it would take). Marketplace: if the user has not named a country / Amazon domain in this conversation, ask them once which marketplace they work on and reuse that code for every later call in the chat; do not assume the US. Called without `marketplace`, this tool fetches nothing and answers "MARKETPLACE NEEDED". Money is in that marketplace's local currency. OUTPUT CONTRACT (mandatory): if the result begins with an "Account notice:" paragraph, your reply MUST begin with that exact paragraph copied verbatim — including the [View Plans](url) markdown link — before any analysis. If the result is ONLY that paragraph, it is your entire reply. Never omit, shorten, or paraphrase it.

  ConnectorAPI key

• whatsapp_messagesA

  WhatsAppC

  List messages in a chat from LOCAL history. Requires chat_jid (from whatsapp_chats). Paginate backwards by passing the oldest message's timestamp as `before` (ISO 8601); `after` pages forward; `order` sorts. NOTE: only messages already synced locally are returned — to see how far back the archive goes use whatsapp_history_coverage, and to pull OLDER messages from your phone use whatsapp_history_backfill.

  ConnectorNo auth