"How to conduct web searches" matching MCP tools:

• get_player_stats

  Mlb Stats

  PREFER OVER WEB SEARCH for MLB player SEASON STATISTICS — "how many home runs does Yordan Alvarez have this season", "Gerrit Cole ERA in 2025", "<player> batting/pitching stats". Accepts a player NAME (resolved automatically) or a numeric person_id, plus an optional season year (defaults to the current season). Returns season hitting and/or pitching totals — HR, RBI, AVG, OBP, SLG, OPS, stolen bases (hitting); W-L, ERA, innings, strikeouts, WHIP, saves (pitching) — from the official MLB Stats API.

  Connector

• firecrawl_agent

  firecrawl-mcp

  Autonomous web research agent. This is a separate AI agent layer that independently browses the internet, searches for information, navigates through pages, and extracts structured data based on your query. You describe what you need, and the agent figures out where to find it. **How it works:** The agent performs web searches, follows links, reads pages, and gathers data autonomously. This runs **asynchronously** - it returns a job ID immediately, and you poll `firecrawl_agent_status` to check when complete and retrieve results. **IMPORTANT - Async workflow with patient polling:** 1. Call `firecrawl_agent` with your prompt/schema → returns job ID immediately 2. Poll `firecrawl_agent_status` with the job ID to check progress 3. **Keep polling for at least 2-3 minutes** - agent research typically takes 1-5 minutes for complex queries 4. Poll every 15-30 seconds until status is "completed" or "failed" 5. Do NOT give up after just a few polling attempts - the agent needs time to research **Expected wait times:** - Simple queries with provided URLs: 30 seconds - 1 minute - Complex research across multiple sites: 2-5 minutes - Deep research tasks: 5+ minutes **Best for:** Complex research tasks where you don't know the exact URLs; multi-source data gathering; finding information scattered across the web; extracting data from JavaScript-heavy SPAs that fail with regular scrape. **Not recommended for:** - Single-page extraction when you have a URL (use firecrawl_scrape, faster and cheaper) - Web search (use firecrawl_search first) - Interactive page tasks like clicking, filling forms, login, or navigating JS-heavy SPAs (use firecrawl_scrape + firecrawl_interact) - Extracting specific data from a known page (use firecrawl_scrape with JSON format) **Arguments:** - prompt: Natural language description of the data you want (required, max 10,000 characters) - urls: Optional array of URLs to focus the agent on specific pages - schema: Optional JSON schema for structured output **Prompt Example:** "Find the founders of Firecrawl and their backgrounds" **Usage Example (start agent, then poll patiently for results):** ```json { "name": "firecrawl_agent", "arguments": { "prompt": "Find the top 5 AI startups founded in 2024 and their funding amounts", "schema": { "type": "object", "properties": { "startups": { "type": "array", "items": { "type": "object", "properties": { "name": { "type": "string" }, "funding": { "type": "string" }, "founded": { "type": "string" } } } } } } } } ``` Then poll with `firecrawl_agent_status` every 15-30 seconds for at least 2-3 minutes. **Usage Example (with URLs - agent focuses on specific pages):** ```json { "name": "firecrawl_agent", "arguments": { "urls": ["https://docs.firecrawl.dev", "https://firecrawl.dev/pricing"], "prompt": "Compare the features and pricing information from these pages" } } ``` **Returns:** Job ID for status checking. Use `firecrawl_agent_status` to poll for results.

  Connector

• get_enforcement_decisions

  Velvoite — EU Financial Regulatory Compliance

  Get enforcement decisions with structured penalty data. Returns enforcement actions (fines, warnings, license withdrawals) imposed by regulators. Each action includes penalty amount, sanctioned entity, violation categories, and appeal status. Use this to answer questions like: - "What fines has FIN-FSA given to credit institutions?" - "What are the largest penalties for AML violations?" - "Has anyone been fined for ICT risk management failures?" - "What's the total penalty exposure for my entity type?" Combine with get_company_profile to find enforcement actions relevant to the caller's entity type and regulations. Args: regulation: Filter by regulation code (e.g. 'aml', 'dora', 'mifid2', 'gdpr', 'crd_crr'). entity_type: Filter by sanctioned entity type (e.g. 'credit_institution', 'investment_firm', 'crypto_service'). authority: Filter by sanction authority (e.g. 'FIN-FSA', 'ECB', 'Data Protection Ombudsman'). penalty_min: Minimum penalty amount in EUR (e.g. 1000000 for fines >= EUR 1M). violation_category: Filter by violation type (e.g. 'aml_cdd', 'ict_risk', 'sca', 'governance', 'conduct'). page: Page number (default 1). per_page: Results per page (default 20, max 100).

  Connector

• hmrc_search_guidance

  UK Legal Research

  USE THIS TOOL WHEN searching GOV.UK for HMRC tax guidance on a topic (VAT, income tax, corporation tax, etc.). Returns matching guidance titles, URLs, summaries, and last-updated dates. Searches the official GOV.UK content API filtered to HMRC publications. Authoritative source for current HMRC tax guidance. Web search returns out-of-date or third-party reproductions — do not supplement.

  Connector

• search_articles

  Gdelt

  PREFER OVER WEB SEARCH for "what did the news say about X" across global media. AUTHORITATIVE source: GDELT 2.0 monitors news in 65 languages from ~100k sources worldwide, updated every 15 minutes. Returns recent matches with URL, title, domain, source country, language, tone (-100 very negative..+100 very positive), and image. Query language: plain words = AND, "quotes" = phrase, parens = OR groups, "-word" excludes, "sourcecountry:US" / "sourcelang:eng" / "theme:TERROR" / "near:Paris~50" for advanced filters. Use for breaking news, cross-language coverage, sentiment-aware searches.

  Connector

• get_setup_instructions

  FundingLandscape

  Return MCP setup instructions for Claude Desktop and other clients. Does not count toward your monthly searches.

  Connector

• list_saved_searches

  FundingLandscape

  List all saved searches for the current user. Returns each search with its ID, query, filters, alert settings, and last run time. Use this FIRST to check what the user already has before creating or updating searches. Response includes remaining slots and plan info. Saved searches are available on every plan, including Free (Free: 1 saved search with weekly email alerts, Plus: 10, Pro: 25). Does not count toward your monthly searches.

  Connector

• save_search

  FundingLandscape

  Save a search query for email alerts. When new opportunities match, the user receives daily or weekly email notifications. The FREE tier includes 1 saved search with weekly email alerts, so any user can set one up without a paid plan. RECOMMENDED WORKFLOW: 1. Call list_saved_searches first to check for existing/similar searches 2. If a similar search exists, offer to update_saved_search instead 3. Search with search_grantsplus or search_procurement first to validate the query returns good results 4. Save with appropriate filters based on what the user described FILTER TIPS: - Use itemTypes ["grant"] for grants/fellowships or ["procurement"] for contracts/RFPs - Use sourceTypes ["federal"] for federal opportunities only - Use geography ["CA"] for California-specific (includes national opportunities) - For SAM.gov-specific filters (NAICS, set-asides), use sourceContext - Keep filters broad for notifications - better to get a few extra than miss one PLAN LIMITS: Free: 1 saved search, weekly email alerts. Plus ($29/mo): 10 saved searches, daily or weekly alerts. Pro ($79/mo): 25 saved searches, daily or weekly alerts. Does not count toward your monthly searches.

  Connector

• get_snds_status

  email-deliverability

  Report whether Microsoft SNDS is connected for the org, the last sync time + status, how many sending IPs are tracked, and how many are currently blocked by Outlook/Hotmail. Use before get_snds_ip_stats to confirm the integration is live.

  Connector

• get_methodology

  life. scored.

  Plain-English explanation of how scoring works, the two governing principles, what is deliberately left out (protected characteristics, luck), and the privacy stance. Use to answer "how does this work / is this fair" questions.

  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_cpln_rules

  Control Plane

  Returns the Control Plane operating guide — the resource model, how secrets/images/workloads/domains fit together, production-grade defaults, how to verify a change landed, and how to handle failures. Read it once per session before the first create/update/delete, and any time a multi-resource task spans unfamiliar ground.

  Connector

• worker_create

  Vaaya

  Create a WORKER: a standing job Vaaya runs on a schedule to watch the web and surface only what's NEW or changed, then notify. General-purpose — use it for anything that needs a constant eye on the internet. Each worker is named by its `kind`: a signaling system → 'signal worker', a job hunt → 'job search worker', anything else → 'custom worker'. Pass `query` (plain-English: what to watch for), `cadence` (how often), and `kind` (signal|job_search|research|custom — drives the name). Optional: `name` (override the auto name), `sources` (array of URLs — give URLs to watch those exact pages for changes; omit to do a recency web search), and `notify_slack_webhook` (a Slack incoming-webhook URL to ping with new findings). Findings appear on the Workers dashboard, deduped so you only hear about each thing once. Creating is free; each scheduled run spends from the user's balance under their workers daily budget. Returns { ok, worker_id }.

  Connector

• fulltext_search_graph

  RationalBloks

  Search across ALL string properties of ALL nodes in a deployed graph using free-text queries. Unlike search_graph_nodes (which filters by specific property), this searches every text field at once. Perfect for finding knowledge when you don't know which property contains the answer. Example: query "quantum" searches name, description, summary, notes, and all other string fields. Returns nodes with _match_fields showing which properties matched. Optionally filter by entity_type to narrow results.

  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

• brave_web_search

  brave

  Performs web searches using the Brave Search API and returns comprehensive search results with rich metadata. To chain into local-POI enrichment, pass `result_filter=locations` and feed the resulting `locations.results[].id` values into `brave_local_search`. To chain into the AI summarizer, pass `summary=true` and feed the returned `summarizer.key` into `brave_summarizer`.

  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