Native Research MCP
Related Servers
Alternatives to Native Research MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to perform deep web research by searching, fetching, chunking, retrieving, and synthesizing cited answers from exact source passages via a deep_research tool.-
- AlicenseAqualityDmaintenanceEnables real-time web search via DeepSeek's search-enhanced dialogue, providing search results as answers through MCP tools.1MIT
- AlicenseAqualityDmaintenanceEnables real-time web search via DeepSeek's server-side tool without requiring additional search API keys.112 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to retrieve verified web evidence via headless Chromium rendering, sitemap navigation, and search candidate discovery, returning clean Markdown, structured JSON, and verbatim quoted proof.5 npmMIT
- AlicenseAqualityBmaintenanceEnables finding information online, reading web pages, finding images, capturing screenshots, and performing multi-source research with per-answer confidence.5AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to run local-first web research: intent-routed search across independent engines with reranking, a multi-stage fetch/crawl ladder, and document extraction. Results come back as signed-cursor, citation-bearing evidence envelopes, with an optional separately enabled profile for browser click/type actions.AGPL 3.0
TDQS
Scored across 6 tools
The tools cover distinct research lifecycle stages: start, search, URL read, evidence read, status, and recovery. There is some potential overlap between research_evidence and research_recover, and between deepseek_read_url and research_evidence, but the descriptions clarify saved extraction versus provider fetch versus recovery.
All names use snake_case and coherent domain prefixes: research_* for task lifecycle and deepseek_* for provider actions. The only inconsistency is that some research_* names are verbs (start, recover) while others are resource nouns (evidence, status).
Six tools is well within the 3-15 range and each covers a distinct step in the research workflow. No tool appears redundant or filler.
Core research lifecycle is covered: start, search, read, inspect evidence/status, and recover. Minor gaps remain, such as no explicit finish/synthesize/cancel or list-evidence operation, but agents can work around these via status and evidence IDs.