| FMRS | 51 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 10 / 20 |
|---|
| Security and permissions | 5 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 14 / 20 |
|---|
| Best for | - Authorized security assessment, incident response and threat intelligence teams
- AI agent workflows that need multi-source intelligence correlated in a single conversation
- Analysts wanting ransomware and breach listing data without configuring API keys
- Users already running the companion security MCP servers (hackbrowser-mcp, cve-mcp, osint-mcp-server, etc.)
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users performing intelligence gathering on third-party targets without authorization
- Users who expect every tool to work out of the box (several require paid or requested API keys)
- Users needing Ethereum or Monero blockchain data (Bitcoin only)
- Users needing officially supported Windows operation (only macOS / Linux are tested)
| - 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 third-party API keys from environment variables (HIBP, IntelligenceX, OTX, AbuseIPDB, abuse.ch, Pulsedive, Hudson Rock, Vulners, Hybrid Analysis, PhishTank)
- Communicate with a local Tor daemon over the local SOCKS5 port (default 127.0.0.1:9050)
- Make outbound HTTPS requests to 16 external data sources
- Install locally and run a process over stdio via npx / Bun
| - 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 | - Dark web intelligence gathering is legally and compliance sensitive — proper authorization is essential
- Tor .onion tools leak DNS if attribution is not routed through the proxy; the project mitigates this with socks5h but users should verify their proxy setup
- API keys live in plain environment variables and could leak into logs or config files
- Tor-dependent tools are unavailable without a local Tor daemon
- Free tiers have low rate limits, so bulk queries may be throttled
- Upstream sources (e.g. ransomware.live, RansomLook, PhishTank) depend on scraping frequency, so data may lag or be incomplete
- All content returned by external sources is untrusted input and should not be executed as instructions
| - 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, Claude Desktop, Cursor, Windsurf | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 66 | 11 |
|---|