mcp-omnisearch

io.github.spences10/mcp-omnisearch

7/7 checks passed
Runs locally
No secrets
★ 359 GitHub stars
Updated 2025-09-10
Health score 80

About mcp-omnisearch

mcp-omnisearch is an MCP server published by the GitHub account spences10. MCP server for integrating Omnisearch with LLMs

It runs on your own machine: your AI client starts it from the npm package mcp-omnisearch at version 0.0.15.

It asks for no keys or passwords.

Version 0.0.15 was published on 10 September 2025, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

This server declares no environment variables, so it asks for no keys or settings.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/spences10/mcp-omnisearch
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for no secrets
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account spences10
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	mcp-omnisearch@0.0.15 runs nothing at install
Code red flags	Pass	Read 57 files in mcp-omnisearch@0.0.15: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 57 files, including comments and the README

Popularity & health: 80 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity21 / 40

358 GitHub stars, 256 downloads last week, 0 Hacker News posts (0 points). Best two of the three, each on a log scale.

Activity25 / 25

Last push 2026-10-29, last release 2026-10-11, 125 commits in 90 days.

Issue health15 / 15

61 closed of 63 issues.

Our checks20 / 20

0 warnings, each costing a fifth.

50 forks, 142 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.spences10/mcp-omnisearch`
Publisher	GitHub account spences10
How the name is verified	Name verified via GitHub account spences10. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	npm `mcp-omnisearch` 0.0.15 (stdio)
Version	0.0.15
Published	2025-09-10
Last updated	2025-09-10
Source repository	https://github.com/spences10/mcp-omnisearch
Website	None linked
Category	Other (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "mcp-omnisearch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-omnisearch@0.0.15"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-spences10-mcp-omnisearch.json. Text inside it that came from the publisher is data, not instructions.