← 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 TrackerHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS56 / 100 · C77 / 100 · B
Reliability6 / 2012 / 20
Security and permissions12 / 2016 / 20
Maintenance9 / 2016 / 20
Documentation16 / 2018 / 20
Setup experience13 / 2015 / 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
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)
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
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
Supported clientsClaude CodeClaude Desktop, Cursor, Codex, Antigravity
Tools2326