← 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 TrackerFirecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS56 / 100 · C75 / 100 · B
Reliability6 / 2013 / 20
Security and permissions12 / 2012 / 20
Maintenance9 / 2016 / 20
Documentation16 / 2017 / 20
Setup experience13 / 2017 / 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
  • Scenarios needing clean, structured web context fed to an AI assistant
  • Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
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
  • Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
  • Sites that explicitly disallow automated access (robots.txt)
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 a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
  • firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
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
  • Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
  • firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
Supported clientsClaude CodeClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools2311