mcp-omnisearch
mcp-omnisearch is an MCP server published by Scott Spence; its MCP spec-revision support has not been verified yet. It is a community implementation. Last verified 2026-09-15.
Does mcp-omnisearch support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision mcp-omnisearch supports (as of 2026-09-15).
Is mcp-omnisearch a first-party (official) MCP server?
No. mcp-omnisearch is a community-published MCP server from Scott Spence, not a first-party vendor server (last verified 2026-09-15).
How do I connect to mcp-omnisearch?
mcp-omnisearch is available via the package npm:mcp-omnisearch, the official MCP Registry under io.github.spences10/mcp-omnisearch, the source repository at https://github.com/spences10/mcp-omnisearch. Authentication: api_key. Transports: stdio.
What tools does mcp-omnisearch expose?
mcp-omnisearch exposes 4 tools, including web_search, ai_search, github_search, web_extract (last verified 2026-09-15).
When were mcp-omnisearch's facts last verified?
2026-09-15. Each fact on this page links to the sources used to verify it.
Which tools does mcp-omnisearch expose?
4 tools verified.
web_searchai_searchgithub_searchweb_extract
mcp-omnisearch gives a single MCP interface to seven external search and
extraction services: Tavily, Brave, Kagi (including Kagi FastGPT), Exa AI,
Linkup, Firecrawl, and GitHub code search via the octokit dependency. It
exposes four tools, web_search, ai_search, github_search and
web_extract, over stdio only; there is no remote or streamable-http
transport. Authentication is per-provider: the operator sets whichever of
TAVILY_API_KEY, KAGI_API_KEY, BRAVE_API_KEY, GITHUB_API_KEY,
EXA_API_KEY, LINKUP_API_KEY or FIRECRAWL_API_KEY it has, and providers
without a configured key are skipped rather than causing an error.
The server is maintained by Scott Spence (GitHub account spences10), an individual developer whose public profile and blog show no affiliation with any of the seven providers it wraps. The io.github.spences10 registry namespace only verifies control of that GitHub account, not any vendor relationship, so authority is community rather than first_party for any of the fronted services.
No spec revision is named anywhere in the README, docs, package.json or the registry record. The official registry entry is also stale: it still reflects version 0.0.15, published 2025-09-10, while npm has since shipped to 0.1.0 (published 2026-08-25) and at least fifteen further version bumps; the repository's own committed server.json still targets the older 2025-07-09 schema rather than the 2025-09-29 schema the live registry API now serves. No security advisories have been published against the repository.
How widely adopted is mcp-omnisearch?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: registry-record
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.spences10/mcp-omnisearch, re-fetched 2026-09-15 via search - version 0.0.15, package npm mcp-omnisearch with stdio transport, publishedAt and updatedAt both 2025-09-10 (never refreshed since initial publish) - accessed
- Repository metadata, fetched 2026-09-15 - spences10/mcp-omnisearch, MIT, 348 stars, 52 forks, last push 2026-09-14, not archived; description names Tavily, Brave, Kagi, Exa, Linkup, Firecrawl and GitHub search as the fronted services; owner is a GitHub User account (Scott Spence) - accessed
- Repository README, fetched 2026-09-15 - "A Model Context Protocol (MCP) server that provides unified access to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl through four consolidated tools"; lists per-provider API-key env vars and states providers without a key are skipped - accessed
- npm registry metadata for mcp-omnisearch, fetched 2026-09-15 - dist-tags.latest 0.1.0 (published 2026-08-25), dependencies are tmcp/@tmcp/* packages and octokit, no @modelcontextprotocol/sdk dependency at all, sole maintainer "spences10" - accessed
- Repository's committed server.json, fetched 2026-09-15 - still declares schema 2025-07-09 and version 0.0.15, confirming the checked-in file and the live registry record have both fallen behind the npm package's 0.1.0 release - accessed
- GitHub user spences10, fetched 2026-09-15 - type User, name "Scott Spence", blog scottspence.com, company null, bio unrelated to any fronted search provider - accessed