updated 2026-11-10 04:07 UTC

MCP Omnisearch

Repository by spences10

🔍 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.

MCP Servers TypeScript Listed MIT

Is MCP Omnisearch safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.1 / 10
Provenance None
Signed commits 100%
Last push 3d ago
Advisories None known
Compare MCP Omnisearch

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Omnisearch scores 60.7/100 (Grade C), ranked #680 of 1374 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; no published advisory affects its latest release (mcp-omnisearch); last pushed 2026-11-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Omnisearch could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships MCP Omnisearch and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/spences10/mcp-omnisearch, MIT, last pushed 2026-11-07. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Not linked

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mcp-omnisearch 0.3.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 5.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues MCP Omnisearch’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How MCP Omnisearch compares in MCP Servers

  1. #370 macOS Calendar and Reminders 60.7 ±0
  2. #371 MCP Zenml 60.7 ±0
  3. #372 MCP Omnisearch 60.7 this agent
  4. #373 tdmcp — TouchDesigner MCP server 60.7 ±0
  5. #374 Yahoo Finance 60.7 ±0

Bars show each HVTrust score; the tick marks MCP Omnisearch’s 60.7.

Where the 60.7 comes from

HVTrust dimensions vs the MCP Servers average

60.7 / 100 · 100.0% confidence

MCP Omnisearch MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.4 / 25
0.6 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.0 / 20
5.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.2 / 20
1.6 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-05
Rank Moved
Rank rose 18 spots (#688 → #670)
2026-10-28
Rank Moved
Rank dropped 19 spots (#647 → #666)
2026-10-19
Rank Moved
Rank dropped 22 spots (#614 → #636)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View MCP Servers Report missing data
67.2
Activity sub-score · out of 100
#372
In MCP Servers

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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
358
Forks
49
Last Push
2026-11-07
3 days ago
Commits (4 wk)
34
Downloads (7d)
183
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #680

Analysis

Activity Inputs

67.2 / 100
StarsRepository reach
15.3 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
19.3 / 25
CommunityFork signal
7.9 / 20

Common questions about MCP Omnisearch

MCP Omnisearch has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does MCP Omnisearch publish package provenance?
No published build provenance is currently detected for MCP Omnisearch. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Omnisearch have an OpenSSF Scorecard?
MCP Omnisearch has an OpenSSF Scorecard score of 5.1/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Omnisearch actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does MCP Omnisearch use?
MCP Omnisearch ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Omnisearch's commits signed?
100% of the last 100 commits to MCP Omnisearch are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Firecrawl, Tavily
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 25HVTrust 4Grade 4Scorecard 1Delisted 1Listed 1MCP 1Surface 1
2026-11-05
Rank Moved
Rank rose 18 spots (#688 → #670)
2026-10-28
Rank Moved
Rank dropped 19 spots (#647 → #666)
2026-10-19
Rank Moved
Rank dropped 22 spots (#614 → #636)
2026-10-14
Rank Moved
Rank rose 26 spots (#630 → #604)
2026-10-12
Rank Moved
Rank dropped 12 spots (#610 → #622)
2026-10-11
Rank Moved
Rank rose 11 spots (#621 → #610)
2026-10-09
Rank Moved
Rank dropped 10 spots (#609 → #619)
2026-10-06
Rank Moved
Rank dropped 12 spots (#600 → #612)
2026-10-01
Rank Moved
Rank rose 11 spots (#602 → #591)
2026-09-24
Rank Moved
Rank dropped 14 spots (#589 → #603)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Firecrawl, Tavily
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 115 spots (#704 → #589)
2026-09-23
HVTrust Changed
HVTrust up 30.7pts (30.8 → 61.5)
2026-09-22
Newly Listed
First tracked at rank #704
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 11 spots (#590 → #579)
2026-09-08
Rank Moved
Rank dropped 14 spots (#539 → #553)
2026-09-07
Rank Moved
Rank dropped 35 spots (#504 → #539)
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 595 spots (#1091 → #496)
2026-09-05
HVTrust Changed
HVTrust up 23.0pts (38.2 → 61.2)
2026-09-04
Rank Moved
Rank dropped 19 spots (#1072 → #1091)
2026-09-03
Grade Changed
Trust grade C → D
2026-09-03
Rank Moved
Rank dropped 678 spots (#394 → #1072)
2026-09-03
HVTrust Changed
HVTrust down 23.1pts (61.2 → 38.1)
2026-09-01
Scorecard Added
OSSF Scorecard: 5.0/10
2026-09-01
Grade Changed
Trust grade D → C
2026-09-01
Rank Moved
Rank rose 650 spots (#1039 → #389)
2026-09-01
HVTrust Changed
HVTrust up 28.0pts (33.2 → 61.2)
2026-08-31
Rank Moved
Rank dropped 34 spots (#1005 → #1039)
2026-08-30
Rank Moved
Rank dropped 53 spots (#952 → #1005)
2026-08-29
Rank Moved
Rank dropped 46 spots (#906 → #952)
2026-08-28
Rank Moved
Rank dropped 32 spots (#874 → #906)
2026-08-27
Rank Moved
Rank dropped 26 spots (#848 → #874)
2026-08-26
Rank Moved
Rank dropped 105 spots (#743 → #848)
2026-08-16
Rank Moved
Rank dropped 15 spots (#725 → #740)
GitHub → npm: mcp-omnisearch

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-omnisearch.svg)](https://hvtracker.net/agents/mcp-omnisearch)
HTML:
<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

Data sources
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.4 · Raw JSON