| FMRS | 61 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 8 / 20 | 10 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 |
|---|
| Maintenance | 14 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 11 / 20 | 14 / 20 |
|---|
| Best for | - Research and analysis agents that need citable page evidence.
- PDF workflows requiring tables, layout, and visual evidence.
- Teams seeking local-first document processing with trust reports.
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Workflows that only need a simple plain-text dump.
- Assuming complete pure-Rust Document Twin capabilities; the README states that pure Rust is still a work in progress.
- Unspecified remote authentication, write, or collaboration features.
| - 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 server needs access to read the local PDF paths supplied in requests.
- URL loading, if used, must comply with configured host, private-IP, size, and HTTP policies.
- OCR and visual-enrichment providers are configured by the deployment environment; requests cannot select arbitrary executables or arbitrary provider URLs.
| - 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 | - PDFs may contain hostile, misleading, or prompt-injection-like content.
- Hidden text, nearly invisible text, overlapping text, unsafe links, and redaction signals may affect extraction or trust assessment.
- OCR, table extraction, and visual analysis can produce low-confidence results and should be checked against rendered pages or crops.
- The README and server manifest identify different product versions, so the intended version should be confirmed before installation.
| - 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, Cursor, VS Code | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 3 | 11 |
|---|