| FMRS | 64 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 10 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 15 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 14 / 20 |
|---|
| Best for | - Developers adding web scraping/data extraction capabilities to AI agents without building their own crawlers
- Users of Claude, Cursor, VS Code, or ChatGPT who want dynamic discovery and use of Apify Store scraping tools
- Autonomous agents that need to pay per Actor run via prepaid tokens (AGI, x402, or Skyfire)
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Tasks that don't need internet scraping, such as pure local filesystem or database work
- Users without an Apify account who are unwilling to authenticate via OAuth or API token
- Fully offline setups that must avoid sending any data to the Apify platform
| - 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 an Apify API token (Bearer) or OAuth login to an Apify account
- Runs Actors and reads run status, dataset, and key-value store data on behalf of the user's account
- Needs outbound network access to reach the Apify API and the external websites Actors scrape
| - 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 | - Running Actors incurs cost, paid via prepaid balance, AGI, direct x402, or Skyfire
- Telemetry (tool-call usage data) is collected by default, and stdio mode also enables Sentry error tracking by default unless opted out
- Dynamic tool discovery lets the agent invoke arbitrary third-party Actors from Apify Store, whose behavior and data handling are outside this server's control
- Scraped website data passes through the Apify API; users are responsible for ensuring scraping complies with target sites' terms of service
| - 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 clients | Claude Desktop, Claude.ai, Claude Code, Cursor, VS Code, ChatGPT, OpenCode, Kiro, Apify Tester MCP Client | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 19 | 11 |
|---|