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.

DimensionBountyLens MCP ServerConnect Claude Code to your BountyLens Hunter TrackerBioMCPOne binary. One grammar. Evidence from the biomedical sources you already trust.
FMRS56 / 100 · C75 / 100 · B
Reliability6 / 2010 / 20
Security and permissions12 / 2016 / 20
Maintenance9 / 2018 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Security researchers with a BountyLens Pro subscription who run bug bounty hunts or authorized pentests from the terminal using Claude Code
  • Individual hunters or teams who want findings, leads, testing notes, and report drafting tied directly into their AI assistant workflow
  • Biomedical researchers
  • Clinicians
  • AI agents that need efficient access to biomedical literature and data analysis
Not for
  • Users without a BountyLens account or Pro subscription
  • Teams that need to work with a different vulnerability-management platform outside the BountyLens ecosystem
  • Anyone looking for automated scanning or exploitation tooling — this server only logs, searches, and surfaces intelligence, it doesn't perform any active scanning or attacks
  • 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 a BountyLens API key (via the BOUNTYLENS_API_KEY environment variable) that has read/write access to your account's sessions, entries, reports, and program intelligence
  • Network access to call the BountyLens API (default bountylens.com, or a self-hosted BOUNTYLENS_URL)
  • 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 API key leaks, an attacker could read or tamper with all your hunt sessions, findings, and unsubmitted report drafts — which may contain sensitive vulnerability details
  • delete_session, delete_entry, and delete_report actions are permanent and unrecoverable, so accidental use can destroy hunt work
  • Draft reports and other content sync in real time to the web dashboard, so local terminal access should be controlled
  • The API is rate limited to 60 requests/minute per key, so heavy bulk operations can be throttled
  • 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 CodeClaude Desktop, Claude Code, Codex, Other MCP stdio clients
Tools2311