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.

DimensionAnansi MCP ServerSelf-healing, conversational scraper for hostile sitesBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS59 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Developers needing robust web scraping
  • Researchers scraping data in adversarial environments
  • Teams wanting AI agents to handle scraping tasks autonomously
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Developers needing legal, low-risk scraping
  • Users targeting only static sites without anti-bot challenges
  • Scenarios with strict legal constraints on scraping
  • 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
  • Making network requests and scraping public data
  • Using a browser for rendering via Playwright
  • Using proxies that provide access to a proxy service
  • Writing exported files locally
  • 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
  • May violate a site's Terms of Service or applicable laws (e.g., CFAA, GDPR)
  • Anti-bot features could be interpreted as circumventing access controls
  • Proxies and IPs may get blocked by target sites
  • Overly aggressive crawling may overload target servers
  • 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 Code, Claude Desktop, Cursor, Windsurf, ChatGPT, LangChain, OpenAI Agents SDKClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1711