"General search query" matching MCP tools:

• search_reviews

  Cochrane Medical Reviews

  Search Cochrane systematic reviews via PubMed. Finds Cochrane Database of Systematic Reviews articles matching your query. Returns PubMed IDs, titles, and publication dates. Use get_review_detail with a PMID to get the full abstract. Args: query: Search terms for finding reviews (e.g. 'diabetes exercise', 'hypertension treatment', 'childhood vaccination safety'). limit: Maximum number of results to return (default 20, max 100).

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• search_notes

  anamnese

  Search notes by keyword or list recent notes. Returns summaries (id + description) only. Use get_note to retrieve the full content of a specific note. With query: Case-insensitive keyword search on description and content. Without query: Returns most recently updated notes.

  Connector

• search_blog

  self-hosted-ai

  Search the Sovereign AI Blog for articles matching a natural language query, optionally filtered by tag and sorted by relevance or date. Behaviour matrix: - query='', sort=* -> list newest-first, optionally tag-filtered - query!='', sort=relevance -> TF-IDF ranked, optionally tag-filtered - query!='', sort=date_desc -> TF-IDF filtered (score > 0.001), then sorted by date Pure read-only, deterministic for a given KB snapshot.

  Connector

• perspective_list

  Perspective AI

  Lists perspectives — either browsing one workspace or searching by title across every workspace the user can access. Items include perspective_id, title, status, conversation count, and workspace info. Behavior: - Read-only. - Browse mode (workspace_id, no query): lists every perspective in that workspace. - Search mode (query): matches against the perspective title across accessible workspaces. Optional workspace_id narrows the search. Query must be non-empty and ≤200 chars. - Errors with "Please provide workspace_id to list perspectives or query to search." if neither is given. - Pass nextCursor back as cursor; has_more indicates further results. When to use this tool: - Resolving a perspective_id from a name the user mentioned (search mode). - Browsing a workspace's perspectives to pick or summarize. When NOT to use this tool: - Inspecting one known perspective in detail — use perspective_get. - Aggregate counts or rates — use perspective_get_stats. - Fetching conversation data — use perspective_list_conversations or perspective_get_conversations. Examples: - List all in a workspace: `{ workspace_id: "ws_..." }` - Search by name across all workspaces: `{ query: "welcome" }` - Search within a workspace: `{ query: "welcome", workspace_id: "ws_..." }`

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• tourradar_vertex-review-search

  MolTravel

  [tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.

  Connector

• search_data

  Opendata Ademe

  Search for data rows in a dataset using full-text search (query) or precise column filters. Returns matching rows and a filtered view URL. Use to retrieve individual rows. Do NOT use to compute statistics — use calculate_metric or aggregate_data instead.

  Connector

• search_data

  Opendata Koumoul

  Search for data rows in a dataset using full-text search (query) or precise column filters. Returns matching rows and a filtered view URL. Use to retrieve individual rows. Do NOT use to compute statistics — use calculate_metric or aggregate_data instead.

  Connector

• get_platform_info

  Makuri Showcase (CogniLedger)

  Returns general information about the Makuri platform, including mission, target users, founding details, and company information. Use this tool when the user asks 'what is Makuri', 'who made it', or wants a general overview.

  Connector

• search_blog

  Sovereign AI Blog

  Search the Sovereign AI Blog for articles matching a natural language query, optionally filtered by tag and sorted by relevance or date. Behaviour matrix: - query='', sort=* -> list newest-first, optionally tag-filtered - query!='', sort=relevance -> TF-IDF ranked, optionally tag-filtered - query!='', sort=date_desc -> TF-IDF filtered (score > 0.001), then sorted by date Pure read-only, deterministic for a given KB snapshot.

  Connector

• search_community

  MetaMask Embedded Wallets (Web3Auth) MCP

  Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). Use for troubleshooting real user issues, finding workarounds, and checking if an issue is known. Provide a query to search or a topic_id to read the full discussion.

  Connector

• search_memories

  anamnese

  Search user memories by keyword, type, tags, or date range. With query: Case-insensitive keyword search on content. Without query: Returns memories by recency. Use type filter to search only facts or only moments.

  Connector

• search

  cyclesite-mcp-server

  OpenAI deep-research / company-knowledge compatibility. Search Cyclesite's active UK used-bike listings by free-text query (matches title, brand, model). Returns the canonical OpenAI shape: { results: [{ id, title, url }] }. Use the id to call fetch() for the full document.

  Connector

• batch_search

  AnySearch

  Run multiple searches in parallel and return all results merged into one response. ## When to use Use batch_search instead of multiple sequential search calls when you have 2–5 independent queries. This saves context window space by returning all results in a single tool call. ## Constraints - Maximum 5 queries per call - Each query item has the same structure as the search tool parameters - Queries run in parallel; a single query failure does not block others ## Example Instead of: search(query=A) → search(query=B) → search(query=C) Use: batch_search(queries=[{query:A,...}, {query:B,...}, {query:C,...}])

  Connector

• search

  AnySearch

  Execute a search and return ranked Markdown results (title, URL, snippet). ## Two modes ### Mode 1 — General web search (no list_domains needed) Omit domain and sub_domain entirely. Use when the query is open-ended and does not target a specific structured data source. Example: search(query="what is quantum computing") ### Mode 2 — Vertical search (call list_domains first) Use when the query targets a specific domain: stocks, patents, flights, CVEs, weather, academic papers, etc. Steps: 1. Call list_domains to get the sub_domain and mandatory query format for the target domain. 2. Pass domain + sub_domain from list_domains output. Never guess them. 3. Format query exactly as specified in the query_format column — wrong format = wrong results. **IMPORTANT: For any query that may belong to a supported vertical domain, ALWAYS call list_domains first — vertical search produces significantly better results than general web search.** ## Decision rule — which mode to use Use Mode 2 (vertical) when ANY of these apply: - Query involves a ticker, DOI, CVE, IATA code, patent number, address, or other structured identifier - Query targets a specific vertical: finance, legal, academic, security, travel, geo, environment, etc. - User asks for real-time or specialized data (stock price, weather, flight status, drug info, etc.) Use Mode 1 (general) when the query is purely conversational or open-ended with no structured lookup. ## After getting results — when to call extract Search returns titles + snippets only. Call extract when: - The snippet is truncated or insufficient to answer the question - User asks to read, summarize, or get details from a specific URL - You need to verify a claim or fact from the source page - The answer requires data only visible in the page body (tables, sections not in snippet) ## Query decomposition One intent per search call. For 2–5 independent queries use batch_search instead. WRONG: search(query="AAPL price and earnings and analyst rating") RIGHT: batch_search(queries=[{query:"AAPL price",...}, {query:"AAPL earnings",...}])

  Connector

• query.capabilities

  CodeReclaimers Capability Oracle

  Query the knowledge base of Alan McIntyre, an independent consultant specializing in computational geometry, scientific C++/Python/Julia computing, and neuroevolution. Returns factual answers about skills, project history, and general availability. Does not make commitments, schedule engagements, or negotiate terms. Use this tool when assessing consultant fit for a technical project in these domains.

  Connector

• fetch_open_tickets

  Sweeppea MCP

  Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_open_tickets ## When to use Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)

  Connector

• brave_place_search

  brave

  Searches Brave's Place Search API. A single call may populate any combination of `results` (POIs), `cities`, `addresses`, `streets`, and `location` (the resolved search area), depending on the query shape. Use for POIs near coordinates or a named area, browsing general POIs (omit `query`, supply coords or `location`), disambiguating bare city names, resolving specific addresses, or looking up streets. Anchor via `latitude`+`longitude` or `location`; with neither, `query` is required.

  Connector

• bitrix-search

  Bitrix MCP

  Search Bitrix24 REST docs by natural-language query and return a short plain-text list of matches (method/event/article/app doc) with name, type, and brief description. Use the exact name/title from results when calling details tools. Optional filters: `limit` and `doc_type` (method|event|other|app_development_docs).

  Connector