M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionLocal Deep Research (LDR) MCP ServerLocal-first deep research assistant exposing multi-engine search and cited reports to Claude over MCP.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS70 / 100 · B75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance18 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Privacy-conscious researchers and developers who want to run LLMs and search fully locally
  • Users already running local models via Ollama, LM Studio, or llama.cpp
  • People who want to give Claude multi-engine academic search and structured report generation
  • Local, STDIO-based integration into Claude Desktop or Claude Code
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Multi-user or network-exposed deployments — this MCP server has no built-in authentication or rate limiting and is documented as local-use only
  • Users wanting a zero-config tool — it requires configuring an LLM provider and a search engine, and sometimes deploying SearXNG
  • Teams needing real-time multi-user collaboration features
  • Users needing to write to upstream databases (read-only)
  • Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
  • Users expecting all advanced features without API keys
Required permissions
  • Access to a configured LLM (local endpoint or cloud API key)
  • Outbound network access to call configured search engines (arXiv, PubMed, SearXNG, Brave, etc.), unless restricted to local documents only
  • Local filesystem read access for analyze_documents to work with private documents
  • Read/write access to the local encrypted (SQLCipher) database
  • Requires internet access to query public biomedical APIs
  • Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
  • Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
Risks and side effects
  • The docs explicitly warn this MCP server is designed for local use only via STDIO transport, has no built-in authentication or rate limiting, and should not be exposed over a network without additional security controls
  • Credentials (e.g. API keys) are held in process memory during active sessions, a routine runtime risk the project mitigates with session-scoped credential lifetimes and core dump exclusion
  • Research queries are sent to whichever search engines are configured, and cloud LLM providers (OpenAI, Anthropic, Google, etc.) receive query/document content when selected
  • Docker's --network host mode can silently fail to expose ports or misroute localhost on Windows/WSL2/Mac
  • Upstream API rate limits may affect performance
  • Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
  • Features requiring API keys (e.g., OncoKB) may be incomplete without them
  • Local binary installations need regular updates for compatibility
Supported clientsClaude Desktop, Claude CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools811