← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionCrawlbase MCP ServerConnect AI agents to real-time web data with JS rendering and anti-bot protection.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS50 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions10 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • AI developers needing real-time web data.
  • Users integrating live data into Claude, Cursor, or Windsurf.
  • Scraping tasks requiring structured outputs (HTML, Markdown, screenshots).
  • Users needing async large-scale crawling with cloud storage.
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Scenarios not requiring real-time data and relying only on training data.
  • Users wanting fully local processing without external API dependencies.
  • Users needing complex custom crawler logic beyond simple fetching.
  • Strict compliance environments that do not allow third-party services.
  • 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 Crawlbase tokens (normal and JS) to access the API.
  • Network access: server must connect to Crawlbase services for crawling.
  • In HTTP mode, tokens can be provided via environment variables or request headers.
  • 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
  • Dependency on Crawlbase service availability and API limits.
  • Traffic to target sites may be blocked or violate their terms of service.
  • Misconfiguration or invalid tokens can cause failures.
  • Free tokens may have rate limits affecting large-scale use.
  • 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 Code, Cursor, WindsurfClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools711