@bountylens/mcp
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@bountylens/mcpSave the XSS on /search to my current session"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@bountylens/mcp
MCP server for BountyLens — connect Claude Code to your Hunter Tracker.
Push findings, leads, tested endpoints, and full report drafts directly from your terminal to the BountyLens dashboard. Everything you log during a hunt session appears in real-time in the web UI with an MCP badge.
Quick Start
1. Get an API key
Go to bountylens.com/dashboard/settings → Integrations → Generate New API Key.
Copy the key — it's only shown once.
2. Add to Claude Code
Add to your MCP config at ~/.claude/.mcp.json:
{
"mcpServers": {
"bountylens": {
"command": "npx",
"args": ["-y", "@bountylens/mcp"],
"env": {
"BOUNTYLENS_API_KEY": "bl_your_key_here"
}
}
}
}3. Restart Claude Code
The BountyLens tools will be available immediately. No other setup needed.
Tools
Sessions
Tool | Description |
| List hunt sessions — filter by |
| Start a new hunt session with a title and optional program |
| Get a session with all its entries and counts |
| Update title, status, or notes |
| Permanently delete a session and all its entries and reports |
Entries
Tool | Description |
| List entries in a session — filter by |
| Log a validated finding with severity, endpoint, method, and description |
| Log a promising lead that needs further investigation |
| Mark an endpoint or feature as tested |
| Add a freeform note to the session |
| Update an entry's title, description, status, or severity |
| Remove an entry |
| Add up to 50 entries in one call — for batch logging findings, leads, or tested endpoints |
Reports
Tool | Description |
| Create a report draft — include summary, steps to reproduce, impact, and remediation |
| List all report drafts in a session |
| Edit a report's title, body, or status (draft/ready/submitted) |
| Permanently delete a report |
Programs
Tool | Description |
| Search bug bounty programs by name or handle |
Usage Examples
During a hunt in Claude Code, the LLM uses these tools automatically based on your instructions:
"List my active sessions"
→ bountylens_list_sessions with status=active
"Save this XSS finding to my Shopify session"
→ bountylens_add_finding with title, severity, endpoint, description
"What leads do I have open on the Uber hunt?"
→ bountylens_list_entries with type=lead
"Mark /api/auth as tested, CSRF tokens are present"
→ bountylens_add_tested with endpoint and description
"Draft a report for the SSRF finding"
→ bountylens_draft_report with full report body
"Push reports/ssrf-uber.md to my Uber session"
→ reads the file, calls bountylens_draft_report with contentsEnvironment Variables
Variable | Required | Default | Description |
| Yes | — | API key from dashboard settings |
| No |
| Custom instance URL (self-hosted) |
API Reference
The MCP server wraps the BountyLens API v1. All endpoints require a Bearer token in the Authorization header.
GET /api/v1/sessions — list sessions
POST /api/v1/sessions — create session
GET /api/v1/sessions/:id — get session + entries
PUT /api/v1/sessions/:id — update session
DELETE /api/v1/sessions/:id — delete session
GET /api/v1/sessions/:id/entries — list entries
POST /api/v1/sessions/:id/entries — create entry
POST /api/v1/sessions/:id/entries/bulk — bulk create entries (max 50)
PUT /api/v1/sessions/:id/entries/:entryId — update entry
DELETE /api/v1/sessions/:id/entries/:entryId — delete entry
GET /api/v1/sessions/:id/reports — list reports
POST /api/v1/sessions/:id/reports — create report
PUT /api/v1/sessions/:id/reports/:reportId — update report
DELETE /api/v1/sessions/:id/reports/:reportId — delete report
GET /api/v1/programs?q=search — search programsRate limit: 60 requests/minute per API key.
Security
API keys are SHA-256 hashed in the database — never stored in plaintext
Keys are shown once on creation and cannot be retrieved
All queries are parameterized — no SQL injection
Every request verifies resource ownership — no IDOR
Pro subscription is validated on every API call
Rate limited to prevent abuse
Requirements
Node.js 18+
BountyLens Pro subscription
API key from the dashboard
Contributing
We welcome contributions. See CONTRIBUTING.md for guidelines.
License
MIT — see LICENSE
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bountylens/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server