Is MCP server for integrating Omnisearch with LLMs safe to use?

MCP server for integrating Omnisearch with LLMs has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install MCP server for integrating Omnisearch with LLMs?

MCP server for integrating Omnisearch with LLMs supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can MCP server for integrating Omnisearch with LLMs do?

MCP server for integrating Omnisearch with LLMs provides 4 tools: web_search, ai_search, github_search, web_extract. See the full tools list on the server page for descriptions and parameters.

What AI clients work with MCP server for integrating Omnisearch with LLMs?

MCP server for integrating Omnisearch with LLMs is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.

Is MCP server for integrating Omnisearch with LLMs actively maintained?

MCP server for integrating Omnisearch with LLMs is actively maintained — last commit was 1 day ago. It has 312 GitHub stars.

MCP server for integrating Omnisearch with LLMs

312 4 tools GitHub

No known CVEs

No license

Actively maintained

Last commit 1d ago

Works with most clients

Transport: stdio, http

4 tools · ~751 tok

Grade B · 0.4% of 200K ctx

Edit this pageView history

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-omnisearch": {
      "env": {
        "EXA_API_KEY": "your-exa-key",
        "KAGI_API_KEY": "your-kagi-key",
        "BRAVE_API_KEY": "your-brave-key",
        "GITHUB_API_KEY": "your-github-key",
        "LINKUP_API_KEY": "your-linkup-key",
        "TAVILY_API_KEY": "your-tavily-key",
        "FIRECRAWL_API_KEY": "your-firecrawl-key",
        "FIRECRAWL_BASE_URL": "http://localhost:3002"
      },
      "args": [
        "/path/to/mcp-omnisearch/dist/index.js"
      ],
      "command": "node",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-spences10-mcp-omnisearch)](https://mcppedia.org/s/io-github-spences10-mcp-omnisearch)

Read me

What MCP server for integrating Omnisearch with LLMs does

A Model Context Protocol (MCP) server that provides unified access to multiple search providers and AI tools. This server combines the capabilities of Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl to offer comprehensive search, AI responses, and content processing through four consolidated tools.

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

70/100across 5 weighted dimensions

How we score →

0255075100

−30

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (4)

Click any tool to inspect its schema.

~751 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is MCP server for integrating Omnisearch with LLMs safe to use?: MCP server for integrating Omnisearch with LLMs has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install MCP server for integrating Omnisearch with LLMs?: MCP server for integrating Omnisearch with LLMs supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can MCP server for integrating Omnisearch with LLMs do?: MCP server for integrating Omnisearch with LLMs provides 4 tools: web_search, ai_search, github_search, web_extract. See the full tools list on the server page for descriptions and parameters.
What AI clients work with MCP server for integrating Omnisearch with LLMs?: MCP server for integrating Omnisearch with LLMs is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is MCP server for integrating Omnisearch with LLMs actively maintained?: MCP server for integrating Omnisearch with LLMs is actively maintained — last commit was 1 day ago. It has 312 GitHub stars.

Similar servers

Others in search

View all →

Brave Search MCP Server98

Web and local search using Brave Search API

86.4k 2

Modelcontextprotocol96

The official MCP server implementation for the Perplexity API Platform

2.2k 4

Tavily Mcp96

Production ready MCP server with real-time search, extract, map & crawl.

2.0k 4

Context795

Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

56.3k 2

MCP Security Weekly

Get CVE alerts and security updates for MCP server for integrating Omnisearch with LLMs and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-omnisearch": {
      "env": {
        "EXA_API_KEY": "your-exa-key",
        "KAGI_API_KEY": "your-kagi-key",
        "BRAVE_API_KEY": "your-brave-key",
        "GITHUB_API_KEY": "your-github-key",
        "LINKUP_API_KEY": "your-linkup-key",
        "TAVILY_API_KEY": "your-tavily-key",
        "FIRECRAWL_API_KEY": "your-firecrawl-key",
        "FIRECRAWL_BASE_URL": "http://localhost:3002"
      },
      "args": [
        "/path/to/mcp-omnisearch/dist/index.js"
      ],
      "command": "node",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-spences10-mcp-omnisearch)](https://mcppedia.org/s/io-github-spences10-mcp-omnisearch)

Read me

What MCP server for integrating Omnisearch with LLMs does

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

README

mcp-omnisearch

A Model Context Protocol (MCP) server that provides unified access to Tavily, Brave, Kagi, Exa AI, GitHub, Linkup, and Firecrawl through four consolidated tools.

Quick start

pnpm install
pnpm run build
node ./dist/index.js

Configure the server in your MCP client with whichever provider keys you have. Providers without keys are skipped and the rest keep working.

{
	"mcpServers": {
		"mcp-omnisearch": {
			"command": "node",
			"args": ["/path/to/mcp-omnisearch/dist/index.js"],
			"env": {
				"TAVILY_API_KEY": "your-tavily-key",
				"KAGI_API_KEY": "your-kagi-key",
				"BRAVE_API_KEY": "your-brave-key",
				"GITHUB_API_KEY": "your-github-token",
				"EXA_API_KEY": "your-exa-key",
				"LINKUP_API_KEY": "your-linkup-key",
				"FIRECRAWL_API_KEY": "your-firecrawl-key"
			}
		}
	}
}

Tools

`web_search`

Search the web with Tavily, Brave, Kagi, Exa, or Kagi Enrichment.

{
	"query": "sveltekit remote functions site:docs.svelte.dev",
	"provider": "brave",
	"limit": 10
}

`ai_search`

Get sourced AI answers with Kagi FastGPT, Exa Answer, or Linkup.

{
	"query": "Explain the differences between REST and GraphQL",
	"provider": "kagi_fastgpt"
}

`github_search`

Search GitHub code, repositories, or users.

{
	"query": "filename:remote.ts @sveltejs/kit",
	"search_type": "code",
	"limit": 5
}

`web_extract`

Extract, crawl, scrape, summarize, or find similar content with Tavily, Kagi, Firecrawl, or Exa.

{
	"url": "https://example.com/long-article",
	"provider": "kagi",
	"mode": "summarize"
}

Documentation

Provider selection — choose providers by task, key, mode, and capability.
Search operators — operator support matrix and tested examples.
Large results — inline vs file response behavior and remote deployment caveats.
Deployment — MCP client, WSL, Docker, cloud, and Firecrawl setup.
Troubleshooting — keys, access, validation, rate limits, and common failures.

Environment variables

TAVILY_API_KEY
KAGI_API_KEY
BRAVE_API_KEY
GITHUB_API_KEY
EXA_API_KEY
LINKUP_API_KEY
FIRECRAWL_API_KEY
FIRECRAWL_BASE_URL optional, for self-hosted Firecrawl
OMNISEARCH_LARGE_RESULT_MODE optional, file default or inline

Development

pnpm install
pnpm run build
pnpm test

Please read CONTRIBUTING.md before opening a PR.

License

MIT License - see LICENSE.

Acknowledgments

Built on Model Context Protocol, Tavily, Kagi, Brave Search, Exa AI, Linkup, and Firecrawl.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

70/100across 5 weighted dimensions

How we score →

0255075100

−30

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Inventory

Tools (4)

Click any tool to inspect its schema.

~751 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is MCP server for integrating Omnisearch with LLMs safe to use?: MCP server for integrating Omnisearch with LLMs has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install MCP server for integrating Omnisearch with LLMs?: MCP server for integrating Omnisearch with LLMs supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can MCP server for integrating Omnisearch with LLMs do?: MCP server for integrating Omnisearch with LLMs provides 4 tools: web_search, ai_search, github_search, web_extract. See the full tools list on the server page for descriptions and parameters.
What AI clients work with MCP server for integrating Omnisearch with LLMs?: MCP server for integrating Omnisearch with LLMs is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is MCP server for integrating Omnisearch with LLMs actively maintained?: MCP server for integrating Omnisearch with LLMs is actively maintained — last commit was 1 day ago. It has 312 GitHub stars.