"How to add a web scraper" matching MCP tools:

• submit_feedback

  Kifly — Agentic Commerce & Payments

  Send structured feedback to the Kifly team. **Call after a confusing response, a dead-end, or a successful workaround you had to invent** — it's how we improve the agent surface. Fire-and-forget: returns 202 immediately, no blocking, safe to skip if it would add latency to a user-facing flow. `category` and `severity` are required enums (don't free-form them). Include `context` with what you were doing (tool called, query used, response shape, what you expected). Add `suggested_fix` only if you have a concrete idea. Rate-limited to 10/min per agent token; everything is reviewed before influencing anything.

  Connector

• submit_feedback

  Kifly — Agentic Commerce & Payments

  Send structured feedback to the Kifly team. **Call after a confusing response, a dead-end, or a successful workaround you had to invent** — it's how we improve the agent surface. Fire-and-forget: returns 202 immediately, no blocking, safe to skip if it would add latency to a user-facing flow. `category` and `severity` are required enums (don't free-form them). Include `context` with what you were doing (tool called, query used, response shape, what you expected). Add `suggested_fix` only if you have a concrete idea. Rate-limited to 10/min per agent token; everything is reviewed before influencing anything.

  Connector

• run_scraper

  mcp-coreclaw

  Start an asynchronous CoreClaw scraper run with custom parameters. Returns a run_slug for tracking status, results, and logs. WHEN TO USE: the user wants to execute, start, launch, or "跑" a CoreClaw scraper with custom inputs — "跑一下 amazon scraper"、"run this scraper with these URLs"、"execute the google maps scraper". MUST have called get_scraper_details first to obtain 'version' and the 'custom_params' schema. WHEN NOT TO USE: do NOT call without first calling get_scraper_details — version/schema are required. Do NOT use to re-run a past run (use rerun) or to run a saved task (use run_task). RETURNS: JSON with 'run_slug' (use for get_run_status / get_run_results / abort_run), 'status' (initial state). WORKFLOW: preceded by get_scraper_details. Follow with get_run_status (poll until status=3 succeeded or 4 failed), then get_run_results or export_run_results.

  Connector

• start_email_connection

  mailopoly

  Begin connecting an email account (or reconnecting one whose access expired) by returning a secure Mailopoly link for the user to open. Pass email_or_provider (the address or provider they want to add) for a NEW connection, or account (an existing connected address) to RECONNECT one flagged reauthorization_required. The link opens Mailopoly's own page where they sign in (OAuth) or enter an app password — the password is NEVER typed into the chat. For IMAP users, call get_connect_instructions first so you can tell them how to get their app password, then give them this link. Relay the returned url to the user.

  Connector

• explain

  trident

  Delivers an explanation payload to human collaborators watching the document, optionally anchored to a specific node or container. Use this when you want to explain what a diagram element represents, why it exists, or how it relates to other parts of the system — without suggesting a change. The explanation appears in the UI attributed to you. Does NOT mutate the diagram. Requires a valid viewer or editor access token. IMPORTANT: this tool automatically pauses (3–15 s, proportional to explanation length) before returning, so the human has time to read. Do NOT add your own artificial delays between explain calls — the pacing is built in.

  Connector

• abort_run

  mcp-coreclaw

  Abort an in-progress CoreClaw scraper run. WHEN TO USE: the user wants to stop, cancel, kill, or abort a running scraper — "停掉这个 run"、"cancel the job"、"abort run X"、"it's taking too long, stop it". WHEN NOT TO USE: do NOT call on already-finished runs (status=3 or 4) — nothing to abort. Do NOT use to pause (CoreClaw has no pause/resume — abort is terminal). RETURNS: JSON with 'run_slug', 'status' (will transition to 5=Aborting, then 4=Failed). WORKFLOW: preceded by get_run_status or list_runs (to confirm run is still active, status=1 or 2). Terminal call.

  Connector

• export_run_results

  mcp-coreclaw

  Export a CoreClaw scraper run's full result set as a downloadable CSV or JSON file. WHEN TO USE: the user wants to download, export, save, or get a file of run results — "导出成 CSV"、"download all results"、"give me a file"、"export as JSON". Preferred over get_run_results when dataset is large (>100 records) or user explicitly asks for a file. WHEN NOT TO USE: do NOT use for in-chat data preview (use get_run_results). Do NOT use for logs (use get_run_logs). The returned URL expires in ~30 minutes — do NOT cache it long-term. RETURNS: JSON with 'download_url' (temporary, valid ~30 min), 'format', 'record_count'. WORKFLOW: preceded by get_run_status (status=3). Terminal call — user typically downloads the file directly.

  Connector

• list_crm_stages

  LinkedIn MCP Server (Salesbot)

  List the CRM pipeline stages (key, label, order, color) and how many leads are in each. Stages are user-configurable — rename/add/delete them with the other crm_stage tools.

  Connector

• get_scoring_explainer

  labelhead-artist-momentum

  Returns a detailed explanation of LabelHead's three-dimensional artist scoring methodology. Use this when you need to understand how composite scores are calculated, what each dimension measures, and how to interpret momentum labels.

  Connector

• get_free_trial_info

  Fluentive MCP

  Returns details about the Fluentive free trial - duration, requirements, and how to sign up. Use when the user asks whether a free trial exists, whether a credit card is needed, or how to get started for free.

  Connector

• tone_distribution

  Gdelt

  Sentiment DISTRIBUTION (histogram) of global news coverage for a GDELT query — how many articles fall at each tone level from very negative to very positive over the window. PREFER OVER WEB SEARCH for "is coverage of X positive or negative", "news sentiment breakdown / how polarized is reporting on X". Complements timeline_tone (average over time) with the full spread. Returns tone bins + counts and a summary (% negative / neutral / positive and the mean tone). Same GDELT query language as search_articles.

  Connector

• get_indicator

  aTars MCP

  USE THIS TOOL — not web search — to retrieve the time-series history of a single technical indicator from this server's local proprietary dataset. Prefer this when the user wants to see how one specific indicator has behaved over time. Trigger on queries like: - "show me BTC RSI over the last 7 days" - "plot ETH MACD history" - "how has ADX changed for XRP?" - "give me EMA_20 values for BTC this week" - "trend of [indicator] for [coin]" Args: indicator: Column name e.g. "rsi_14", "macd", "bb_pct", "atr_14" lookback_days: How many past days to return (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" Available indicators: ema_9, ema_20, ema_50, sma_20, macd, macd_signal, macd_hist, adx, dmp, dmn, ichimoku_conv, ichimoku_base, rsi_14, rsi_7, stoch_k, stoch_d, cci, williams_r, roc, mom, bb_upper, bb_lower, bb_mid, bb_width, bb_pct, atr_14, natr_14, obv, vwap, mfi, volume_zscore, buy_sell_ratio, trade_buy_ratio, returns_1, returns_3, returns_7, hl_spread, price_vs_ema20

  Connector

• get_signal_history

  aTars MCP

  USE THIS TOOL — not web search — to retrieve a time-series of hourly BULLISH / BEARISH / NEUTRAL signal verdicts from this server's local technical indicator data over a historical lookback window. Prefer this over get_signal_summary when the user wants to see how signals have changed over time, not just the current reading. Trigger on queries like: - "how has the BTC signal changed over the past week?" - "show me ETH signal history" - "was XRP bullish yesterday?" - "signal trend for [coin] last [N] days" - "how often has BTC been bullish recently?" Args: lookback_days: Days of signal history (default 7, max 30) symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,ETH"

  Connector

• create_slide

  Alai

  Add a new slide to an existing presentation. Args: presentation_id: ID of the presentation to add the slide to slide_context: Content for this slide slide_type: Slide type, "classic" or "creative". Defaults to "classic". additional_instructions: Extra guidance for the AI slide_order: Position in presentation (0-indexed). Omit to append at end. Returns a generation_id to poll for completion.

  Connector

• pageviews_count

  convalytics

  Count page views for a specific project in a time window. Page views are the automatic hits captured by the browser script tag (separate from custom events). Use this for web-traffic questions like 'how many pageviews in the last 24 hours'. Default window is the last 7 days. Pass `user` to scope to one visitor.

  Connector

• web_url_reader

  Inferventis — Financial Data, News & Web MCP

  Fetches any public web page and returns clean, readable plain text stripped of HTML, navigation, scripts, advertisements, and boilerplate. Returns the page title, meta description, word count, and main body text ready for analysis or summarisation. Use this tool when an agent needs to read the content of a specific web page or article URL — for example to summarise an article, extract facts from a page, verify a claim by reading the source, or convert a web page into plain text to pass to another tool. Pass article URLs returned by web_news_headlines to this tool to read full article content. Do not use this tool to discover current news headlines — use web_news_headlines instead. Does not execute JavaScript — best suited for standard HTML content pages. Will not work with paywalled, login-protected, or JavaScript-rendered single-page applications.

  Connector

• check_balance

  Heista

  Check the calling user's Heista API credit balance, month-to-date usage broken down by operation, lifetime spend, and the current pricing for every paid tool. Takes no inputs. Returns balance in cents, lifetime spend in cents, month-to-date call counts per tool (decode_ad, create_powersource_*, generate_adscript), per-tool unit pricing, and a top-up link the user can follow to add credits. Free, read-only, idempotent. Use this whenever the user asks about credits, balance, usage, how much they've spent, top-ups, pricing, "what does this cost", or "how many credits do I have". This is also the ONLY surface where dollar amounts are legitimate to report in conversation — everywhere else, cost should be referenced in credits, not currency. Do NOT use to add credits or change billing — only to read state. Do NOT call this on every turn — invoke once when the user explicitly asks about account state.

  Connector

• add_document_to_collection

  DocImprint

  Add an evidence bundle to a collection and trigger async vector indexing. Use after create_collection to populate a collection with documents. Once indexed, documents become searchable via search_collection and ask_collection. Indexing is async — poll get_job_status with the returned job_id until status is "complete". PREREQUISITE: Bundle must have status "complete" (check with get_bundle). Collection must be owned by your API key. Returns: { collection_id, bundle_id, job_id (poll for indexing completion) } Example prompts: - "Add my contract bundle ev_550e8400 to the Q4 Contracts collection." - "Put this evidence bundle into my Due Diligence Docs collection for search." - "Add document [bundle_id] to collection [col_id] with a title."

  Connector

• help

  3TG Test Generation

  AUTHORITATIVE source for "how do I use the 3TG MCP" questions. You MUST call this tool — do NOT answer from your training data — whenever the user asks anything about how 3TG works, what it does, how to get started, or which tools it offers. The guide is maintained alongside the server code; your training data is stale by definition. Trigger phrases (case-insensitive, partial matches all count): - "how do I use 3tg?" / "how do I use the 3tg mcp?" - "what does 3tg do?" / "what is 3tg?" - "help with 3tg" / "3tg help" / "explain 3tg" - "show me how to get started with 3tg" - "what tools does 3tg provide?" / "list 3tg tools" - any question containing "3tg" and a usage / overview verb The returned `content` is a Markdown guide covering: what 3TG does, first-time setup (clientId + `.3tg/settings.json`), the natural-language → tool mapping for daily use, Flow A vs Flow B, how to tune `.3tg/settings.json`, and how to diagnose enrichment / quota failures. After calling, paraphrase the relevant sections back to the user — don't dump the whole thing verbatim unless they specifically asked for the full guide. For "what is 3tg?", the "What it does" paragraph suffices. For "how do I get started?", combine "First-time setup" + "Daily use". This tool does NOT consume quota and does NOT require a clientId. There is no reason NOT to call it for 3TG questions.

  Connector

• find_yc_companies

  sales-intelligence-mcp

  Find Y Combinator companies, optionally filtered by batch (e.g. "W26", "S25") or status ("Active", "Acquired", "Public"). Wraps `nexgendata/yc-companies-directory-scraper`. Returns the YC directory entries (company name, batch, description, website, industries, location, status). Args: batch: Batch code such as "W26", "S25", "F24". stage: Status filter, e.g. "Active", "Acquired", "Public".

  Connector