Side-by-Side Model Context Protocol Comparison
Agent Search MCP vs Content Core
In-depth architectural comparison of the Agent Search MCP and Content Core 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: 68/100 (Great) | Auth: No auth required
Content Core
Search & Data Extraction · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Agent Search MCP if you need specialized Search & Data Extraction tools running via a local process. Choose Content Core 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: free_search, free_search_advanced, free_extract.
Choose Content Core when:
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (Free / Open Source).
- Primary tools included: URL, file, and text extraction, PDF, office, ebook, and markup support, Audio and video transcription.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Agent Search MCP Tools (7)
free_search
Search the web with an explicit adapter set and bounded fallback.
Best for: Quick fact-finding, general search, when date/domain filters are not needed.
Not recommended for: Filtered or verified-only results — use free_search_advanced. For full page content — use free_extract.
Twelve adapters are selectable; the default request uses DuckDuckGo + Sogou only. Adapters that share one upstream family are tried sequentially on failure and never double-count as corroboration. Explicitly requested optional API adapters run only when credentials are present and the free basket is short or below the quality gate.
Results are deduplicated and include separate confidence, relevance, and source-count signals.
@readOnly true @idempotent true — makes outbound HTTP requests to configured search engines. Injection detection and SSRF protection active.
free_search_advanced
Advanced search with filters and quality control.
Best for: Domain filtering, high-confidence only, Chinese content.
Not recommended for: Simple queries — use free_search instead.
@readOnly true @idempotent true — runs waterfall progressive search across policy-allowed engines. Makes outbound HTTP requests to search engines and optionally to Jina Reader for content enrichment.
free_extract
Extract full content from a URL. Returns clean markdown text.
Best for: Reading a specific page found in search results to get full context.
Not recommended for: Bulk extraction — use free_search first to find relevant pages.
Behavior: Makes an outbound HTTP request to Jina Reader (r.jina.ai) which fetches and converts the page to markdown. Has SSRF protection: blocks private IPs, localhost, and metadata endpoints. 10s request timeout — pages exceeding this will fail with a timeout error. HTTP errors (4xx, 5xx) are returned as structured error responses.
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 Configuration
Content Core Configuration
Frequently Asked Questions
More alternatives to Agent Search MCPMore alternatives to Content CoreSearch & Data Extraction category hub