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.

DimensionSearXNG SearchPrivate web search through SearXNG.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS61 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Users who want self-hosted search infrastructure
  • Teams with an existing SearXNG instance and privacy requirements
  • MCP clients that need paginated search and URL reading
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without an accessible SearXNG instance
  • Users seeking a native SearXNG plugin installation
  • Workflows that require reading PDFs, media, archives, or other binary downloads
  • 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
  • Requires access to the configured SEARXNG_URL, which the manifest marks as required and secret.
  • May use AUTH_USERNAME and AUTH_PASSWORD for legacy global SearXNG Basic Auth.
  • Search queries are passed to external search services, and web_url_read makes requests to user-specified URLs.
  • 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
  • Privacy depends on the connected SearXNG instance and its configuration.
  • Search queries may be passed to external services used by SearXNG.
  • URL reading creates outbound requests; private or internal URLs and redirects are blocked by default, but network deployments should still enable and configure hardening.
  • HTML fallback depends on the instance's page structure and may return fewer results without relevance scores or engine names.
  • 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, CursorClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools411