| FMRS | 57 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 6 / 20 | 10 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 14 / 20 |
|---|
| Best for | - AI agent developers needing broad crypto context — prices, DeFi, wallets, security — from multiple providers in one place
- Teams doing crypto due diligence with Claude, Cursor, VS Code, or other remote-HTTP-MCP clients
- Integrators who want one API key instead of separate upstream provider credentials
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Users who need to self-host or modify the MCP server source (the server is closed-source and managed)
- Users seeking unlimited free usage (credit-based pricing applies)
- General-purpose tasks unrelated to crypto
| - 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 | - Hive API key (Authorization Bearer or X-API-Key header, optional secret)
- Optional upstream provider keys (COINGECKO_PRO_API_KEY, ALCHEMY_API_KEY, HELIUS_API_KEY, MORALIS_API_KEY, TENDERLY_API_KEY, GOPLUS_APP_KEY/SECRET, CODEX_API_KEY, etc.)
| - 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 | - Credit-based billing: each tool call consumes credits and rate limits apply
- Security scores are not investment advice; honeypot/rugpull results may be incomplete or lag
- On-chain text (token names, memos) should be treated as untrusted input with prompt-injection risk
- Data may come from cached or degraded sources; check provenance and freshness labels in responses
- Leaked API keys can be abused; keep keys server-side and rotate them
| - 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, Windsurf, Gemini CLI | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 6 | 11 |
|---|