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.

DimensionAffiliate Networks MCPAsk your affiliate networks in plain English from your AI workspace.BioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS70 / 100 · B75 / 100 · B
Reliability11 / 2010 / 20
Security and permissions14 / 2016 / 20
Maintenance14 / 2018 / 20
Documentation17 / 2017 / 20
Setup experience14 / 2014 / 20
Best for
  • Affiliate publishers who want natural-language access to multiple networks
  • Agencies managing multiple brands' programs
  • Teams needing periodic reporting and anomaly monitoring
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without an AI client (e.g., Claude Desktop)
  • Advertisers needing write operations (e.g., link creation) since advertiser adapters are read-only
  • Clients that are not yet officially supported (e.g., Cursor, VS Code) without testing
  • Networks where clicks are essential, as many adapters lack click support
  • 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
  • Credentials for network APIs (API keys, tokens, etc.)
  • Optional: local file write to `~/.affiliate-mcp/.env` and `brands.json`
  • Optional: anonymous usage telemetry (off by default)
  • Optional: local result cache (off by default; writes files when enabled)
  • 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
  • Experimental community adapters may be unreliable or return inaccurate data.
  • Credentials stored in local files; risk if file permissions are loose or device compromised.
  • Hosted connector stores credentials in encrypted vault but involves third-party service.
  • API calls may incur rate limits or costs depending on the network.
  • Untested client paths may not work; check support status table.
  • 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, Claude CoworkClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools011