← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionDexPaprika MCP ServerReal-time multi-chain DEX and on-chain data via MCPBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS70 / 100 · B75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions16 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • AI assistant users needing multi-chain DEX and on-chain data
  • DeFi analysts and market researchers
  • Developers building token and pool analysis tools
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Scenarios needing on-chain writes, trade execution, or private-key management
  • CEX market data needs (this server focuses on DEX/on-chain data)
  • Users requiring truly real-time data on a free budget (free tier delays up to 15 seconds)
  • 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 internet access to call the DexPaprika API
  • Node.js/npm for local stdio installation
  • No API key needed for the free tier (a free key raises quota)
  • 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
  • Free-tier rate limits (200,000 credits/month per IP, 30 requests/minute) can trigger DP429_RATE_LIMIT errors
  • Free tier data delayed up to 15 seconds; not for truly real-time use
  • Some newer tokens/pools may have incomplete historical data
  • Price and on-chain data are informational only, not investment advice
  • 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 clientsClaude Desktop, Cursor, Claude CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1711