MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
5 safety and 5 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.
Disclosure: Community-maintained MIT MCP server that wraps multiple external search, extraction, AI-answer, and GitHub providers. Users must follow each provider's API, quota, billing, retention, and website-use policies.
{
"mcpServers": {
"omnisearch": {
"command": "npx",
"args": ["mcp-omnisearch"],
"env": {
"TAVILY_API_KEY": "your-tavily-key",
"KAGI_API_KEY": "your-kagi-key",
"BRAVE_API_KEY": "your-brave-key",
"GITHUB_API_KEY": "your-github-token",
"EXA_API_KEY": "your-exa-key",
"LINKUP_API_KEY": "your-linkup-key",
"FIRECRAWL_API_KEY": "your-firecrawl-key"
}
}
}
}Omnisearch MCP Server connects Claude and other MCP clients to multiple search,
AI-answer, GitHub search, and web-extraction providers through four consolidated
tools: web_search, ai_search, github_search, and web_extract.
Use it when Claude needs one MCP interface for provider-backed web search, sourced AI answers, GitHub search, URL extraction, crawling, scraping, summaries, similar-content discovery, or content retrieval.
These sources were reviewed on 2026-06-06. Prefer the live repository, README, npm metadata, license, package metadata, server manifest, provider selection guide, large-results guide, server entrypoint, and tool registry for current setup and behavior details.
Configure at least one provider API key, then launch the server:
{
"mcpServers": {
"omnisearch": {
"command": "npx",
"args": ["mcp-omnisearch"],
"env": {
"TAVILY_API_KEY": "your-tavily-key",
"KAGI_API_KEY": "your-kagi-key",
"BRAVE_API_KEY": "your-brave-key",
"GITHUB_API_KEY": "your-github-token",
"EXA_API_KEY": "your-exa-key",
"LINKUP_API_KEY": "your-linkup-key",
"FIRECRAWL_API_KEY": "your-firecrawl-key"
}
}
}
}
Only include the provider keys you actually intend Claude to use. Use a least-privilege GitHub token when enabling GitHub search.
Omnisearch MCP Server is a broker over multiple external providers. Scope API keys carefully, confirm before crawling or scraping, and respect website terms, robots policies, provider quotas, billing, and retention behavior.
Treat provider keys, GitHub tokens, queries, URLs, extracted content, crawled pages, GitHub results, AI answers, summaries, and large-result files as sensitive. Avoid sending private URLs, proprietary source text, or broad GitHub tokens through providers that should not receive them.
Show that Omnisearch MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/omnisearch-mcp-server)Omnisearch MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | MCP server that unifies web search, AI answer, GitHub search, and web extraction providers including Tavily, Brave, Kagi, Exa, Linkup, Firecrawl, and GitHub behind four consolidated tools. Open dossier | Local-first MCP server for web scraping, crawling, URL mapping, batch extraction, structured extraction, summarization, diffing, brand extraction, and optional hosted API fallback for bot-protected pages. Open dossier | MCP server for the Graphlit platform, enabling Claude to ingest, search, retrieve, organize, and operate on files, web pages, feeds, collections, conversations, memory, connectors, crawls, and RAG-ready project knowledge. Open dossier | No-key multi-engine MCP server, CLI, and local daemon for web search and public web content retrieval across engines such as Bing, DuckDuckGo, Brave, Exa, Baidu, CSDN, Juejin, Startpage, and Sogou. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Scott Spence | WebClaw | Graphlit | Aas-ee |
| Added | 2026-06-06 | 2026-06-06 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Omnisearch MCP Server can query multiple third-party search, AI answer, GitHub search, extraction, scraping, crawling, summarization, and content-processing providers. Firecrawl crawl, scrape, map, extract, and action modes can interact with websites and may trigger robots.txt, TOS, rate-limit, or authentication concerns. GitHub search depends on the configured token scope and can reveal private code, repositories, users, or organization metadata when a broad token is used. Large result mode can write response content to files; review where those files are stored before using it with private or regulated data. Require confirmation before crawling sites, extracting private URLs, using authenticated providers on sensitive targets, or running broad GitHub searches against private organizations. | ✓WebClaw MCP Server can scrape one URL, crawl same-origin links, map URLs, batch multiple URLs, extract structured data, summarize pages, compare snapshots, and extract brand metadata. Scraping, crawling, search, research, and hosted fallback can trigger target-site rate limits, bot protections, legal restrictions, or terms-of-service limits. The server validates public HTTP URLs and rejects private or internal destinations, but operators should still avoid fetching internal, secret, customer-specific, or credential-bearing URLs. Cookie-bearing requests, proxies, and browser profiles can expose authenticated sessions or route traffic through external infrastructure. Setting `WEBCLAW_API_KEY` enables hosted API fallback, which can send target URLs and page context to the WebClaw service. Structured extraction and summarization may use configured LLM providers; review provider data handling before enabling those tools with sensitive pages. | ✓Graphlit MCP Server can ingest files, web pages, messages, posts, emails, issues, text, memory, feeds, crawls, and connected SaaS data into a Graphlit project. Tools can create or delete contents, feeds, collections, conversations, specifications, and workflows, and can configure project defaults when explicitly requested. Web crawling, web search, screenshots, podcast search, feed scheduling, publishing, and connector operations may contact third-party services and process external content. Generated audio and image publishing can call configured model/provider services and consume credits or quota. Require confirmation before ingesting private repositories, emails, drive files, Slack/Teams/Discord data, customer documents, large crawls, generated media, deletion operations, or project configuration changes. | ✓open-webSearch can send search queries to multiple public engines and fetch public web pages, GitHub READMEs, CSDN articles, Juejin articles, and other supported targets. Search and fetch results can be incomplete, stale, rate-limited, blocked, region-dependent, or affected by search-engine ranking and scraping protections. Respect each target site's terms and robots expectations; do not use the server for abusive scraping, credentialed browsing, paywall bypass, or personal-data harvesting. The optional local daemon exposes HTTP endpoints for local tooling; keep it bound to trusted local interfaces and do not treat it as a public internet API. Proxy settings, Playwright WebSocket/CDP endpoints, and reused browser sessions can route traffic or cookies through external systems; configure them deliberately. Leave TLS verification enabled unless a specific target has a broken certificate chain and the risk has been accepted. |
| Privacy notes | ✓Provider API keys, GitHub tokens, search queries, URLs, extracted page content, crawled site maps, scraped text, summaries, AI answers, GitHub search results, and large-result files can be exposed to the MCP client. Search and extraction providers may log queries, URLs, source content, account identifiers, usage metadata, and generated responses according to their own policies. Web extraction can capture personal data, paywalled content, internal URLs, or proprietary documents if supplied by the user or available to an authenticated provider. GitHub search output may include repository names, code snippets, file paths, commit metadata, and organization details. Keep provider credentials in local MCP configuration only, and avoid sharing transcripts that contain private queries, URLs, source text, or tokens. | ✓URLs, fetched page content, crawl results, extracted structured data, snapshots, brand metadata, cookies, proxy settings, API keys, and LLM prompts can be exposed to the MCP client. Crawled pages may include personal data, customer content, non-public links, access tokens embedded in URLs, or site-specific identifiers. Diff snapshots and exported JSON can preserve page content longer than expected; store and delete them according to the workflow's retention needs. Hosted fallback, proxy providers, search/research APIs, and LLM providers may observe target URLs, headers, cookies, prompts, and extracted content when enabled. Redact sensitive URLs and extracted data before sharing MCP transcripts, crawl results, logs, or generated RAG context. | ✓Graphlit environment IDs, organization IDs, JWT secrets, project IDs, resource IDs, connector tokens, URLs, files, emails, messages, issues, transcripts, screenshots, memories, conversations, usage records, and retrieved sources can be exposed to the MCP client. Ingested documents may be extracted to Markdown; audio and video may be transcribed; images and pages may be described or screenshot. Connected services such as Slack, Discord, Google Drive, Microsoft 365, GitHub, Jira, Linear, Notion, Dropbox, Box, Reddit, and Twitter/X can expose private workspace content. Usage records can include request, response, variables, token counts, bytes, units, and credit charges for project operations. Keep Graphlit secrets in local MCP client configuration only, and review retention, deletion, and connector policies before ingesting regulated or customer data. | ✓Search queries, fetched URLs, result titles, snippets, article content, proxy URLs, browser endpoints, and fetched page text can be exposed to MCP clients, logs, and model context. Live search engines and fetched websites may observe queries, IP address, proxy exit, browser fingerprints, cookies, timing, and request headers. Playwright fallback or CDP reuse can expose browser state, existing cookies, logged-in sessions, or verification state to fetched pages. The project includes public URL validation and private-network target protections, but operators should still avoid fetching internal, secret, or customer-specific URLs. Redact sensitive search terms and downloaded page content before sharing transcripts or logs. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude to WebClaw for local-first scraping, crawling, content extraction, structured data, page diffs, brand assets, and public URL guards.
Connect Claude to Graphlit projects for ingestion, retrieval, web crawling, feeds, collections, conversations, memory, and RAG workflows.
Give Claude no-key multi-engine web search and public page fetching through open-webSearch with stdio, CLI, and optional local daemon modes.
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.