MCP Omnisearch
🔍 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.
Is MCP Omnisearch safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Omnisearch
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Omnisearch scores 61.0/100 (Grade C), ranked #606 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.1/10; 100% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Omnisearch compares in MCP Servers
- #340 Xdebug MCP 61.1 +0.1
- #341 Real Browser MCP 61.0 ±0
- #342 MCP Omnisearch 61.0 this agent
- #343 Map Traveler MCP 61.0 ±0
- #344 Home Assistant MCP 61.0 ±0
Bars show each HVTrust score; the tick marks MCP Omnisearch’s 61.0.
Where the 61.0 comes from
HVTrust dimensions vs the MCP Servers average
61.0 / 100 · 100.0% confidenceMCP Omnisearch MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
68.3 / 100Supply Chain Trust
Common questions about MCP Omnisearch
Does MCP Omnisearch publish package provenance?
Does MCP Omnisearch have an OpenSSF Scorecard?
Is MCP Omnisearch actively maintained?
What license does MCP Omnisearch use?
Are MCP Omnisearch's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Omnisearch's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain MCP Omnisearch?
For maintainers
HVTrust scores MCP Omnisearch from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-omnisearch)
<a href="https://hvtracker.net/agents/mcp-omnisearch"><img src="https://hvtracker.net/badge/mcp-omnisearch.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON