Skip to main content
Glama
569,274 tools. Updated 2026-09-14 22:20

"search" matching MCP tools:

  • GET /search — Cross-resource omni-search Cross-resource search across profiles, rooms, messages (incl. private DMs + group DMs you're in), events, and chapters in one round trip. Returns the top-N matches per resource, grouped by resource. Use this when you don't yet know which resource carries the answer — agents typically call this first, then drill into a specific `GET /search/<resource>` for more depth on a single bucket. There's no page param: when you hit the per-resource limit and want more, switch to the per-resource endpoint for that one. The events slice has a baked-in forward-looking default (events ending in the last 30 days or later, and currently enabled) — this matches the in-app "Search across DC" surface. Use `GET /search/events` directly to look further back in time. **Query syntax (`q=`):** plain words match with prefix + typo tolerance. Wrap a phrase in double quotes to require an exact ordered match — e.g. `q="remote work"`. AND/OR/NOT/parentheses are NOT parsed in `q=` — use the structured filter params below for boolean composition.
    ConnectorNo auth
  • Search the user's files by filename and return matching documents in the deep-research result shape. ALIAS: this is the SAME search as search_files (same data, same permissions) - use it when your client requires the id/title/url search contract (ChatGPT deep research); otherwise prefer search_files for richer file metadata. Each result's id can be passed to fetch (or get_file) to read that document. Read-only; nothing is written, so it is safe to call.
    ConnectorNo auth
  • Search JobYap job postings by natural-language query. Matches job titles, falling back to significant keywords when the full phrase finds little. Returns result ids, titles and citable URLs for use with fetch. For structured filtering (location, company, remote, freshness) prefer search_jobs.
    ConnectorNo auth
  • Search Quantustik for S&P 500 tickers by symbol or company name. Paired with fetch — this is the two-tool "search"/"fetch" convention ChatGPT connectors and deep-research clients expect from an MCP server: call search first to get lightweight hits, then fetch(id) on the one(s) worth reading in full. Args: query: Ticker symbol (e.g. "NVDA") or company-name substring (e.g. "nvidia", "apple"). Case-insensitive. Returns a dict with a `results` list of up to 10 {id, title, url} objects — id is the ticker symbol, ranked exact-symbol match first, then company-name/ticker prefix, then substring. Empty query or no scan data returns an empty list, never an error.
    ConnectorNo auth
  • Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides), "lrsf" (laws, regulations, standards, frameworks), or "all". limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, and optionally relationships and full_text).
    ConnectorNo auth
  • Search the TCLP knowledge graph using fusion search (semantic + BM25). Args: query: Free-text search query (max 1000 characters). node_type: Content scope — "tclp" (clauses, glossary terms, guides), "lrsf" (laws, regulations, standards, frameworks), or "all". limit: Maximum number of results to return (1–50). rerank: Whether to apply RRF reranking when combining graph and text results. include_full_text: Include each hit's full body text (Markdown). Off by default — bodies are large; request only when you need the content, and prefer a small `limit` when you do. Returns: JSON with "meta" (totals, timing) and "results" (ranked hits with title, url, content_type, scores, and optionally relationships and full_text).
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    F
    maintenance
    Enables semantic search across documentation stored in Gemini FileSearchStores, returning AI-generated answers with source citations.
    1
    1
    -

Matching MCP Connectors

  • Web search for AI agents. Ranked results with page passages already extracted, plus URL to markdown.

  • Collaborative, cache-first web search for agents — cited answers from a shared live-web pool.

  • Search across your own connected-account content and return the best matches. Each result has an `id` (pass it to `fetch` for the full item), a `title`, a `url`, and a `text` snippet. This is the deep-research "search" entrypoint the ChatGPT/Claude connectors call by convention; for semantic search over analyzed videos specifically use `search_videos`. Returns {"results": [...]}; when you have no connected accounts it returns reason="no_connected_accounts" plus a connect_url instead of results.
    ConnectorOAuth
  • Search the datasheet corpus; returns hit records (metadata + snippet, each with an opaque `ref`). Pass a ref list to `get_segments` for full content. If you already know the part number(s), prefer `lookup` — it fuses this search with `get_segments` in one call and groups full content per part. Use `search` when the part is unknown, or to triage snippets before pulling full content. For part-specific queries, pass scope='device:<MPN>' (e.g. scope='device:NE5532') to restrict hits to that part and avoid cross-part contamination.
    ConnectorNo auth
  • Search the authenticated user life graph. Deterministic routing first: food + relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. Requires OAuth or a supported scoped credential. ($0.15; API key required)
    ConnectorNo auth
  • Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, the AI front desk for clinics, provider-side insurance-claims automation, Cliniko and Nookal integration, security and compliance pages, case studies, pricing and blog posts. Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use. Returns a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic. Read-only and idempotent; no authentication; 60 requests per minute per client. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.
    ConnectorNo auth
  • Hybrid keyword + semantic search over the public pages of vascue.io: healthcare-operations guides, the AI front desk for clinics, provider-side insurance-claims automation, Cliniko and Nookal integration, security and compliance pages, case studies, pricing and blog posts. Use it to answer questions about what Vascue offers, how its products work and what it has published. One topic per call; cite the returned page URL for every excerpt you use. Returns a JSON text payload: result.chunks[] ordered by relevance, each with text (a Markdown excerpt), score (0-1, higher is better) and item.metadata.url (the canonical https://www.vascue.io/... page). Off-topic queries still return the nearest chunks, so treat scores below about 0.5 as weak evidence and say so when the site does not cover a topic. Read-only and idempotent; no authentication; 60 requests per minute per client. Public content only: never send patient information, claim documents, clinic credentials or booking requests. It cannot book appointments or look up clinic data.
    ConnectorNo auth
  • Searches the user's saved projects by title and returns ids with links (the ChatGPT search contract). Use fetch for the detail of one result; list_projects for browsing with filters.
    ConnectorOAuth
  • Search Deal Flow's marketplace deals (the public feed, filtered by this query) and, once this connection is bound to a company, the member's own notes. Returns up to 10 of each as { results: [{id, title, url}] } - each id round-trips into `fetch`. For clients that only speak search/fetch (e.g. ChatGPT's chat connector mode); connections_pulse and connections_execute cover the full native tool roster.
    ConnectorOAuth
  • Search every public dataset on Mostly Right and return up to 20 matches as {results: [{id, title, url}]}, where `id` is the dataset slug and `url` its canonical page. No account needed. Example: {"query": "hourly airport weather observations"}. Pass a result's `id` straight to fetch for the full dataset document. This is the plain search-and-fetch pair; search_datasets is the richer, paged version with topics, publishers and summaries.
    ConnectorNo auth
  • [KEY REQUIRED · no credits, 60/day] law.go.kr에서 **법령명**으로 한국 법령을 검색합니다(조문 본문·판례는 검색하지 않습니다). 판례는 `lookup_precedent`, 조문은 `lookup_statute`, 아무 텍스트의 인용 검증은 `verify_citations` 를 쓰십시오. 입력 예: '주택임대차보호법', '근로기준법'. / Search Korean statutes by **law name** on law.go.kr (it does not search article text or case law). Use `lookup_precedent` for cases, `lookup_statute` for articles, `verify_citations` to check citations in arbitrary text.
    ConnectorNo auth
  • Search VICP vaccine-injury cases by free text. Returns result ids for use with fetch. (Alias of search_cases for deep-research clients; prefer search_cases when structured filters are available.)
    ConnectorNo auth
  • Search Sponsorable's podcast-sponsorship database for brands that sponsor podcasts — the deep-research/Responses-API compatibility interface, paired with fetch. Matches sponsor names and domains and returns citable documents; pass a result's id to fetch for the full profile. For filtered or paginated search (category, industry, recency), use search_sponsors instead.
    ConnectorNo auth
  • Web search returning the top results as markdown, via Jina. Needs a Jina API key (pass via _apiKey) — Jina stopped serving anonymous requests.
    ConnectorNo auth
  • Search the Reactome biological pathway database by keyword across all object types (Pathway, Reaction, Protein, Complex, etc.); returns stable IDs and display names grouped by type.
    ConnectorNo auth
  • Search the EU open-data portal (data.europa.eu) for datasets by free-text query; supports Solr filter expressions (e.g. country.iso:DE), pagination via rows/start, and sorting. Returns dataset titles, descriptions, and publisher info.
    ConnectorNo auth
  • Full-text search across Swiss court judgments, court decisions and case law from entscheidsuche.ch. Covers decisions of the Federal Supreme Court (BGer, BGE) and cantonal courts such as Kantonsgericht, Obergericht or Verwaltungsgericht. Typical use cases: - Search Federal Supreme Court judgments, BGE or rulings by topic - Find Swiss case law on tenancy law, ZGB, OR, StGB or BV - Verify case numbers, judgment numbers or citations - Related tools: fetch_document, search_by_case_number, list_hierarchy, list_facets Search syntax (Lucene query string): - Phrase / case-number search: "BGE 142 III 1" (in quotes) - Boolean operators: AND, OR, NOT (or +, -) - Wildcards: * and ? - The default operator between terms is AND. Filters are combined with AND. Use hierarchy IDs from `list_hierarchy` or `list_facets`. Pagination: after the first call, pass the `next_cursor` value from the response as `search_after` in the next call.
    ConnectorNo auth