DeepSeek × Exa Search Combine MCP
Related Servers
Alternatives to DeepSeek × Exa Search Combine MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP clients to run local web searches with automatic failover across multiple search providers and to extract public web pages as titles and Markdown content, using circuit breaking and key-redacted logging.-
- AlicenseNot gradedqualityBmaintenanceEnables querying multiple search engines and paid search APIs through a local aggregation service, returning deduplicated and RRF-ranked results via a single MCP tool.1MIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server provides a unified search experience by integrating and intelligently fusing results from multiple major search engines. It automates complex processes like query language detection, weighted result ranking, and engine failover to deliver robust and high-quality search output.MIT
- FlicenseNot gradedqualityDmaintenanceA remote MCP server that routes web search queries across multiple providers (HTTP APIs, external MCP servers, LLM with grounding) with intelligent fallback and quota management.-
- AlicenseNot gradedqualityCmaintenanceMCP server for multi-engine web search and web page fetching, supporting parallel search, content extraction, and optional LLM-powered search summarization and deep search.5MIT
- AlicenseBqualityDmaintenanceAggregated search API service that provides real-time web search capabilities for AI assistants via MCP.26 npm43GPL 3.0
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search performs multi-provider web search, fetch retrieves page content for URLs, and status reports backend availability without network calls. There is no meaningful overlap that would cause misselection.
The names are short, lowercase, and consistently action-oriented or state-oriented: search, fetch, status. The pattern is predictable and easy for an agent to map to intent.
Three tools are well scoped for a focused search-and-fetch server. Each tool earns its place, and there are no redundant or filler tools.
The core lifecycle is covered: search the web, fetch full content, and inspect backend status. Minor gaps exist around provider configuration or richer result management, but the essential surface is complete for the stated purpose.