io.github.spences10/mcp-omnisearch
NPM · MCP-OMNISEARCH · SCANNED SEP 26
MCP server for integrating Omnisearch with LLMs
Available components
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 → Why this is hard to score →
Supply Chain Security100
- 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
- 2 of 48 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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 Management90
- Stability observed for 27 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
Tool Safety25
- Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.spences10/mcp-omnisearch server?
io.github.spences10/mcp-omnisearch runs locally as an npm package, launched with npx -y mcp-omnisearch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-omnisearch
claude mcp add spences10-mcp-omnisearch -- npx -y mcp-omnisearch
{
"mcpServers": {
"spences10-mcp-omnisearch": {
"command": "npx",
"args": [
"-y",
"mcp-omnisearch"
]
}
}
} {
"servers": {
"spences10-mcp-omnisearch": {
"command": "npx",
"args": [
"-y",
"mcp-omnisearch"
]
}
}
} codex mcp add spences10-mcp-omnisearch -- npx -y mcp-omnisearch
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"spences10-mcp-omnisearch": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-omnisearch"
],
"enabled": true
}
}
} openclaw mcp add spences10-mcp-omnisearch --command npx --arg -y --arg mcp-omnisearch
mcp_servers:
spences10-mcp-omnisearch:
command: "npx"
args: ["-y", "mcp-omnisearch"] {
"McpServers": {
"spences10-mcp-omnisearch": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-omnisearch"
]
}
}
} assistant mcp add spences10-mcp-omnisearch -t stdio -c npx -a -y mcp-omnisearch
{
"mcpServers": {
"spences10-mcp-omnisearch": {
"command": "npx",
"args": [
"-y",
"mcp-omnisearch"
]
}
}
} 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.
- 26 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
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 26 Sept 2026 · Analysed npm/mcp-omnisearch@0.0.15
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 48 packages
| Packages resolved | 48 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
The sandbox run completed and this package exposed no tools.
What is the io.github.spences10/mcp-omnisearch server?
io.github.spences10/mcp-omnisearch is listed in the public MCP registry as io.github.spences10/mcp-omnisearch. MCP server for integrating Omnisearch with LLMs. This page covers its npm package (mcp-omnisearch).
Is the io.github.spences10/mcp-omnisearch server safe to use?
io.github.spences10/mcp-omnisearch scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.spences10/mcp-omnisearch server expose?
io.github.spences10/mcp-omnisearch exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the io.github.spences10/mcp-omnisearch server still maintained?
io.github.spences10/mcp-omnisearch is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.spences10/mcp-omnisearch server under?
io.github.spences10/mcp-omnisearch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.