| FMRS | 44 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 3 / 20 | 10 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 |
|---|
| Setup experience | 8 / 20 | 14 / 20 |
|---|
| Best for | - Users who want the control loop and state kept on their device
- Users with llama.cpp, Ollama, LM Studio, or another OpenAI-compatible model backend
- Developers needing browser, filesystem, document, and task automation
- Technical users willing to review approvals, traces, and network egress
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users looking for a standalone MCP server that can be installed directly into an MCP client
- Production integrations requiring stable APIs, because the project is still a developer preview
- Environments that cannot allow agent access to browsers, files, shells, or networks
- Systems without Node.js, Chromium, git, or an accessible model backend
| - 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 | - Read and write access to the local state directory and SQLite databases
- Permission to run approved shell commands and perform some process operations
- Access to the configured Chromium browser, browser profile, and websites
- Network access to configured llama-server, cloud models, search providers, or HTTP endpoints
- Permissions required by external MCP servers whose tools are invoked
- Optional macOS Accessibility, Screen Recording, Automation, or Reminders permissions
| - 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 | - Browser navigation, HTTP tools, cloud models, search providers, MCP, Telegram, update checks, and analytics can create network egress
- Shell commands and skills inherit the agent process environment and may access `.env` secrets
- Traces and `.env` under the state directory should be treated as sensitive; the project says redaction and environment filtering are not complete isolation
- Filesystem writes, patches, archive extraction, process termination, HTTP requests, and untrusted MCP tools are policy-gated, but approval errors can still cause harm
- The project is a developer preview, so commands, configuration, and behavior may change
| - 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 Code, Codex, Other MCP stdio clients |
|---|
| Tools | 0 | 11 |
|---|