mcp-omnisearch — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Multi-provider web and content search

What we know

🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi, Exa), AI tools (Kagi FastGPT, Exa, Linkup), and content extraction services (Firecrawl, Tavily, Kagi). Includes GitHub search. All through a single interface. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

GitHub exact repo pushed_at 2026-10-09T18:27:54Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Search provider API keys and submitted queries; costs and data routing vary by provider. Complete write authority is not verified.
Refer to first-party setup documentation; do not infer authorization from package existence.
Sensitive access: queries, search keys and retrieved content

Search provider API keys and submitted queries; costs and data routing vary by provider.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

352 repository stars

Stars observed Oct 10, 2026.

Repository total for spences10/mcp-omnisearch.

All limitations / Review context

Has mcp-omnisearch changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

Search provider API keys and submitted queries; costs and data routing vary by provider.
Public tracking suitability is not an installation safety audit.
Refer to first-party setup documentation; do not infer authorization from package existence.
queries, search keys and retrieved content
Sensitive access: queries, search keys and retrieved content
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Precise setup/auth/permissions not verified
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-09T18:27:54Z

Original activity observations

GitHub exact repo pushed_at 2026-10-09T18:27:54Z

Technical identity

github.com/spences10/mcp-omnisearch

Exact implementation source: https://github.com/spences10/mcp-omnisearch ↗
Reviewed resource type: MCP Server
Repository identity: spences10/mcp-omnisearch

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
spences10/mcp-omnisearch
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher README references MCPick and pnpm; its installer syntax must be confirmed in docs/deployment.md before exposing as a copyable command.
claude code default registration · Publisher instructions
npx mcpick add --name mcp-omnisearch --command npx --args=-y,mcp-omnisearch
Configure / authenticate
MCP100 setup guide
Publisher README recommends MCPick `npx mcpick add --name mcp-omnisearch --command npx --args=-y,mcp-omnisearch`. MCPick is a separate registration tool; confirm the selected MCP host before accepting configuration edits. Search-provider keys are required only for provider integrations.
Check connection
Suggested check
Inspect installed MCP server tools before supplying provider keys.
Remove / uninstall / revoke
MCP100 setup guide
Remove the MCP registration named `omnisearch` (if that is the host entry's name), e.g. `claude mcp remove omnisearch`. If installed from a checkout, stop the running node process and remove that checkout only after preserving local configuration. Client remove command is an MCP100 composed example: replace the registration name with your actual installed name.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove omnisearch

Official Documentation & Sources

What it does

🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi, Exa), AI tools (Kagi FastGPT, Exa, Linkup), and content extraction services (Firecrawl, Tavily, Kagi). Includes GitHub search. All through a single interface. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Multi-provider web and content search

Representative uses

Multi-provider web and content search

Limitations

Search provider API keys and submitted queries; costs and data routing vary by provider.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-09T18:27:54Z

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.
Permissions: Search provider API keys and submitted queries; costs and data routing vary by provider.
Data handling: queries, search keys and retrieved content
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: Search provider API keys and submitted queries; costs and data routing vary by provider.

Access scope and cautions

Write actions: Not verified
Sensitive access: queries, search keys and retrieved content
Risk level: medium
Security notes: Search provider API keys and submitted queries; costs and data routing vary by provider. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Multi-provider web and content search.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Search provider API keys and submitted queries; costs and data routing vary by provider.

What data-handling boundary should I consider?

queries, search keys and retrieved content Recorded sensitive-access context: queries, search keys and retrieved content.

What limitations and risks should I check before use?

Search provider API keys and submitted queries; costs and data routing vary by provider. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Exact GitHub pushed_at 2026-10-09T18:27:54Z. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.