| FMRS | 56 / 100 · C | 77 / 100 · B | 75 / 100 · B |
| Reliability | 6 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 9 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 | 17 / 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
| - Hevy PRO users who want AI assistants to directly access their workout data
- People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
- Anyone needing summaries and insights from their training data
| - 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
| - Users without a Hevy PRO subscription (API key required)
- Users who want to use the server without an API key
- Those needing delete workflows (Hevy API does not expose delete endpoints)
| - 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 HEVY_API_KEY environment variable for Hevy API authentication
- Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
- Read operations can fetch workouts, routines, folders, templates, history, and user info
| - 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
| - API key can be misused if leaked; do not expose in URLs, logs, or screenshots
- Create operations may produce duplicates on retry; update operations replace existing records
- The server sends data to the Hevy API and may send telemetry to external services unless disabled
| - 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 clients | Claude Code | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
| Tools | 23 | 26 | 11 |