mcp-omnisearch

Created By
spences10a year ago
🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi), AI tools (Perplexity, FastGPT), and content processing services (Jina AI, Kagi). Combines search, AI responses, content processing, and enhancement features through a single interface.
Overview

What is MCP Omnisearch?

MCP Omnisearch is a Model Context Protocol (MCP) server that provides unified access to multiple search engines and AI tools, allowing users to perform comprehensive searches and content processing through a single interface.

How to use MCP Omnisearch?

To use MCP Omnisearch, configure your API keys for the desired search engines and AI tools, then interact with the server through its API to perform searches, generate AI responses, and process content.

Key features of MCP Omnisearch?

  • Unified access to multiple search engines (Tavily, Brave, Kagi) and AI tools (Perplexity, FastGPT).
  • Content processing capabilities including summarization and extraction.
  • Flexible API key requirements allowing partial configuration.

Use cases of MCP Omnisearch?

  1. Conducting research by aggregating results from various search engines.
  2. Generating AI responses to queries using real-time web search.
  3. Extracting and summarizing content from web pages for analysis.

FAQ from MCP Omnisearch?

  • Can I use MCP Omnisearch without all API keys?

Yes! You can start with just one or two API keys, and the server will only enable those providers.

  • What types of searches can I perform?

You can perform factual searches, privacy-focused searches, and high-quality authoritative searches.

  • Is there support for content processing?

Yes! MCP Omnisearch includes tools for content extraction, summarization, and enhancement.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
spences10
Star
79
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago