| FMRS | 45 / 100 · D | 75 / 100 · B |
|---|
| Reliability | 6 / 20 | 10 / 20 |
|---|
| Security and permissions | 7 / 20 | 16 / 20 |
|---|
| Maintenance | 11 / 20 | 18 / 20 |
|---|
| Documentation | 11 / 20 | 17 / 20 |
|---|
| Setup experience | 10 / 20 | 14 / 20 |
|---|
| Best for | - Security researchers and analysts
- SOC, threat-intelligence, and fraud investigation teams
- Developers who need MCP-based tool orchestration
- OSINT practitioners conducting lawful authorized investigations
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Unauthorized monitoring of people or organizations
- Illegal data collection, intrusion, or privacy violations
- Users who do not want external APIs, third-party services, or local investigation tools
- Workflows requiring all findings to come from a single verified data source
| - 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 launching a local Python MCP server over stdio.
- The default AI agent requires ANTHROPIC_API_KEY; Ollama or an OpenAI-compatible backend can also be used.
- Optional tools require credentials for HIBP, IPInfo, IP2Location, AbuseIPDB, Shodan, VirusTotal, Censys, GitHub, or Bright Data.
- Requires network access to relevant services; some features depend on holehe, sherlock, sublist3r, and phoneinfoga being available in PATH.
- The REPL saves sessions in ~/.openosint/history/ and reports in reports/.
| - 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 | - Use is limited to legal and authorized security research.
- Investigations may process emails, phone numbers, usernames, IPs, breach records, and other sensitive data.
- Third-party APIs may impose rate limits, charges, data-retention terms, or service restrictions.
- Live dork searches and URL scraping use Bright Data APIs, and calls may be billable.
- External sources may be incomplete, outdated, or produce false positives; findings require human verification.
| - 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 | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 18 | 11 |
|---|