Agent Search Mcp vs TinySearch — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agent Search Mcp vs TinySearch
In-depth architectural comparison of the Agent Search Mcp and TinySearch MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Agent Search Mcp
Search & Data Extraction · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
TinySearch
Search & Data Extraction · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agent Search Mcp if you need specialized Search & Data Extraction tools running via a local process. Choose TinySearch if your workspace requires Search & Data Extraction integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agent Search Mcp when:
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Supports 8+ zero-key search engines including DuckDuckGo, Bing, Baidu, Wikipedia, Multi-source evidence with provenance and partial failure visibility, Configurable request policies to manage paid provider usage and budgets.
You need dedicated capabilities in the Search & Data Extraction domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local hybrid reranking with ONNX embeddings and BM25, Search backend options: DuckDuckGo via DDGS or self-hosted SearXNG, Compact evidence output with source URLs for context.
Free multi-engine MCP search server — 8 free engines (DDG, Sogou, Bing, Baidu, Wikipedia, Startpage, Yandex, Mojeek), waterfall progressive search, multi-source verification, content enrichment, news search, language auto-detection, CLI. Zero API keys needed. npx agent-search-mcp
Self-hosted web research for MCP agents: search (SearXNG, with DuckDuckGo fallback), crawl, dense+BM25 rerank, and dedupe into a source-grounded, cited prompt. Local ONNX embeddings by default, or bring an OpenAI-compatible embedding API.
Category & Scope
Tools & Capabilities Breakdown
Agent Search Mcp Tools (6)
Supports 8+ zero-key search engines including DuckDuckGo, Bing, Baidu, Wikipedia
Multi-source evidence with provenance and partial failure visibility
Configurable request policies to manage paid provider usage and budgets
Automatic language detection for English, Chinese, and other languages
Compact output mode reducing token usage by ~30%
Accessible via CLI, stdio, and Streamable HTTP with no external dependencies
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Agent Search Mcp is categorized under Search & Data Extraction and uses a local stdio subprocess. In contrast, TinySearch belongs to Search & Data Extraction using local stdio subprocess. Select Agent Search Mcp when you need capabilities focused on search & data extraction and TinySearch when you require tools for search & data extraction.