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.

DimensionStripe MCPConnect AI applications and agents to Stripe.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS45 / 100 · D75 / 100 · B
Reliability8 / 2010 / 20
Security and permissions9 / 2016 / 20
Maintenance10 / 2018 / 20
Documentation8 / 2017 / 20
Setup experience10 / 2014 / 20
Best for
  • Teams that need Stripe capabilities in AI applications or agents
  • Developers building Stripe products with MCP, LLM, or agent frameworks
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Applications with no Stripe integration requirement
  • Clients limited to local stdio or SSE and unable to use Streamable HTTP
  • Clients unable to complete OAuth access
  • 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 MCP client must use OAuth to access the remote server
  • Actual Stripe resource permissions depend on the connection and authorization scope; the source does not provide a detailed permission list
  • 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
  • An AI agent may perform Stripe-related actions on a user's behalf, so authorization scope and results should be reviewed
  • The remote server depends on network connectivity and OAuth authorization
  • The source does not specify individual tools or the permission boundary of each operation
  • 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