M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionTomTom Maps MCP ServerTomTom location, search, routing, and traffic data for AI workflows.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS63 / 100 · C75 / 100 · B
Reliability10 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • AI agents needing global geocoding, place search, routing, and traffic data
  • Developers integrating TomTom mapping capabilities with Claude Desktop, VS Code, Cursor, or Windsurf
  • Applications that need HTTP or Docker-based map-service integration
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Applications that do not need TomTom location or navigation data
  • Users who cannot provide a TomTom API key
  • Offline mapping or offline API-data scenarios
  • 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 a valid TomTom API key.
  • The key must have MCP Server access enabled; local tests call real APIs and consume API quota.
  • TomTom Orbis Maps and some EV features may require additional account access.
  • 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
  • The MCP client or operator is responsible for updates, patches, and security configuration of local deployments.
  • API calls consume quota.
  • TomTom Orbis Maps and some EV features are in public preview and may produce 403 errors or be unavailable to some accounts.
  • Map and traffic results depend on TomTom services and the selected backend.
  • 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, GitHub Copilot, Cursor, Windsurf, SmolagentsClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools1611