research_mcp
Related Servers
Alternatives to research_mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that acts as an AI knowledge and skills hub, automatically discovering, indexing, and serving skill libraries to any MCP client with full-text search, rich metadata, and hot reload.MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables saving, retrieving, and managing research content using ChromaDB vector storage and semantic search.5MIT
- FlicenseAqualityDmaintenanceAn MCP server providing tools for web research, code review, and concept explanation, callable by any MCP-compatible client.3-
- FlicenseCqualityDmaintenanceAn MCP server that provides tools, resources, and prompts for reading, writing, and summarizing research notes stored in a local flat-file database.2-
- AlicenseCqualityAmaintenanceAn MCP server for deep research that performs search, scraping, synthesis, fact-checking, and persistent memory, enabling users to conduct comprehensive research tasks via Claude.85 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that utilizes LangGraph and Google Gemini to conduct comprehensive research through multi-iteration deep searches and quick results. It provides high-quality analysis with automated citations and grounding metadata for thorough investigations.2MIT
TDQS
Scored across 27 tools
Each tool targets a distinct stage of the research workflow (search, retrieval, appraisal, synthesis, design, storage), so most are clearly separable. A few adjacent tools — fetch-url vs extract-from-pdf vs fetch-paper, and appraise-evidence vs appraise-source — could be confused at a glance, but descriptions clarify their boundaries.
Tool names are uniformly lowercase and hyphenated, with a dominant verb_noun pattern (search-literature, design-study, check-reporting). A handful of noun-based names (citation-graph, author-profile, people-analytics-preset, workforce-survey-template) break the strict verb-first pattern, but the overall style remains predictable and readable.
With 27 tools, the set exceeds the 25-tool threshold and becomes heavy for an agent to navigate and select from efficiently. While the research domain is broad, several tools could be consolidated (e.g., vault tools, appraisal variants) without losing core functionality.
The tool surface covers the full research lifecycle: question scoping, literature search and retrieval, evidence appraisal, synthesis, study design, ethics, reporting, and knowledge management via Zotero and Obsidian. Minor gaps exist — no delete/update for saved Zotero items or vault notes, and no dedicated structured data-extraction tool — but agents can work around these limitations.