Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.spences10/mcp-omnisearch

NPM · MCP-OMNISEARCH · SCANNED AUG 3

MCP server for integrating Omnisearch with LLMs

Available components

npm · mcp-omnisearch 56
−5 this week 56 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security95
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 22 of 45 dependencies flagged as unhealthy (20 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability58
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 24 tokens (~12/item across 2 items; 0 tools + 2 resources), lean.Pass
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mcp-omnisearch

# add to Claude Code
claude mcp add spences10-mcp-omnisearch -- npx -y mcp-omnisearch
# add to Codex CLI
codex mcp add spences10-mcp-omnisearch -- npx -y mcp-omnisearch
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "spences10-mcp-omnisearch": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-omnisearch"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add spences10-mcp-omnisearch --command npx --arg -y --arg mcp-omnisearch
# ~/.hermes/config.yaml
mcp_servers:
  spences10-mcp-omnisearch:
    command: "npx"
    args: ["-y", "mcp-omnisearch"]
// mcp.json
{
  "mcpServers": {
    "spences10-mcp-omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +35
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Maintenance: unverified → pass ▲ functional
    • Dependency health: unverified → 0.59 ▲ functional
    • License: unverified → pass ▲ functional
    • Stability: unverified → 0.20 ▲ functional
    • Licence: MIT functional
  • 31 Jul 26 +11
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −52
    • Malware scan: pass → unverified ▼ security
    • Provenance: fail → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Install scripts: pass → unverified ▼ security
    • License: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Tool coverage: fail → unverified ▼ functional
    • Maintenance: pass → unverified ▼ functional
    • Dependency health: 0.98 → partial functional
    • Licence: MIT functional
  • 27 Jul 26 +36
    • Provenance: unverified → fail ▼ security
    • Known CVEs: unverified → pass ▲ security
    • Install scripts: unverified → pass ▲ security
    • Security disclosure: unverified → fail ▼ functional
    • Tool coverage: unverified → fail ▼ functional
    • Maintenance: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • License: unverified → pass ▲ functional
    • First check of Schema quality: unverified functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: poor functional
    • Dependency health: partial → 0.98 functional
    • Licence: MIT functional
  • 26 Jul 26 25

    First indexed and scored.

    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 45 packages

45 packages in the resolved dependency tree · 20 deprecated · 2 stale.

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

The sandbox run completed and this package exposed no tools.