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.

DimensionWeChat MCP ServerWeChat MCP Server based on WeiXinMPSDK (WeChat McpRouter)BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS35 / 100 · D75 / 100 · B
Reliability4 / 2010 / 20
Security and permissions6 / 2016 / 20
Maintenance15 / 2018 / 20
Documentation6 / 2017 / 20
Setup experience4 / 2014 / 20
Best for
  • Developers building WeChat applications with .NET / C#
  • Technical evaluators tracking new MCP integration in the Senparc.Weixin SDK
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users needing a stable, production-released MCP server (currently 0.1.0-beta with an unfilled package name)
  • Users outside the .NET stack or without a need for WeChat platform capabilities
  • Users requiring a definite tool list and complete installation documentation
  • 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
  • The source does not state the permissions or scopes required by this MCP server.
  • 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 NuGet package name in the manifest is a placeholder, so the actual installable package cannot be confirmed and installation may fail.
  • The version is 0.1.0-beta, so interfaces and behavior may change at any time.
  • The source provides no tool, authentication or permission details, leaving the security boundary unknown.
  • 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, Claude Code, Codex, Other MCP stdio clients
Tools011