| FMRS | 46 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 4 / 20 | 10 / 20 |
|---|
| Security and permissions | 8 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 |
|---|
| Setup experience | 9 / 20 | 14 / 20 |
|---|
| Best for | - Users who need Claude Code, OpenClaw, Cursor, or Windsurf to access content across multiple platforms
- Individuals and developers seeking free or open-source upstream tools for web research
- Agent workflows that need centralized installation, diagnostics, and backend routing
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Tasks requiring graphical browser interaction, form submission, or automated login
- Deployments requiring a standalone MCP server or a documented MCP transport
- Environments that do not allow shell command execution by the agent
- Use cases requiring every platform to work without login state or cookies
| - 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 | - The agent must execute shell commands, including pip install, system dependency installation, and upstream CLI calls
- Some channels require local browser login state, cookies, or tokens
- Credentials are stored locally in ~/.agent-reach/config.yaml; the README states the file mode is 600
| - 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 | - Cookie- or login-state-based access to Twitter/X, Xiaohongshu, Reddit, and similar platforms may trigger detection, restrictions, or account bans
- The default installation may install Node.js, gh CLI, mcporter, and other system infrastructure, and modify agent skills and MCP configuration
- Platform anti-crawling changes or upstream tool changes may break individual channels
- Server deployments may require a proxy; the README estimates roughly $1 per month
| - 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 Code, OpenClaw, Cursor, Windsurf | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 0 | 11 |
|---|