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.

DimensionWeather MCP ServerA comprehensive MCP server for real-time weather data with Claude DesktopBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS50 / 100 · D75 / 100 · B
Reliability9 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance12 / 2018 / 20
Documentation12 / 2017 / 20
Setup experience9 / 2014 / 20
Best for
  • Developers looking to integrate real-time weather into Claude Desktop
  • Use cases requiring caching for faster responses
  • Developers interested in Clean Architecture and SOLID principles
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without an OpenWeatherMap API key
  • Simple use cases that don't require caching or a database
  • Users who cannot run Docker environments
  • 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
  • Access to external OpenWeatherMap API
  • Read/write to PostgreSQL database (for query history)
  • Read/write to Redis cache
  • Read API keys from environment variables
  • 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
  • API key exposure if not securely stored
  • Database and Redis unavailability could cause failures
  • Cache data may become stale, leading to inaccurate info
  • Dependency on external OpenWeatherMap API, which might have rate limits or downtime
  • 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 DesktopClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools411