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.

DimensionAlby Bitcoin Payments MCP ServerConnect a bitcoin lightning wallet to your LLM via Nostr Wallet ConnectBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS58 / 100 · C75 / 100 · B
Reliability7 / 2010 / 20
Security and permissions8 / 2016 / 20
Maintenance13 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Users who already have an NWC-compatible Lightning wallet and want an LLM to act on it
  • Developers integrating bitcoin payment capability into MCP-capable clients like Claude, Goose, Cline, or Windsurf
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users who don't use the bitcoin Lightning Network or lack an NWC wallet
  • Use with weaker models — the README notes a capable model (e.g. Claude 3.7 Sonnet) is required or the server may not function correctly
  • 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 an NWC connection secret, which grants the server the ability to act on your wallet's funds
  • In hosted/remote mode, this secret is transmitted to the Alby server as a Bearer header or URL parameter
  • 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
  • If the NWC connection secret leaks, anyone holding it can control the associated wallet's funds
  • Passing the secret via a URL query parameter risks it being logged in browser history, server logs, or proxies
  • Relying on a weaker model may lead to unintended or incorrect payment actions
  • 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 Web, Claude Code, Goose Desktop, Goose CLI, Cline, Windsurf, N8NClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011