BountyProof MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOUNTYPROOF_CONTACT | Yes | Contact email address | |
| BOUNTYPROOF_DELAY_MS | No | Delay between preflight requests (milliseconds) | 350 |
| BOUNTYPROOF_MAX_URLS | No | Maximum number of discovered URLs | 100 |
| BOUNTYPROOF_WORKSPACE | No | Workspace directory | |
| BOUNTYPROOF_ALLOW_HTTP | No | Allow unencrypted HTTP | false |
| BOUNTYPROOF_KATANA_BIN | No | Path to Katana executable (if not in PATH) | |
| BOUNTYPROOF_NUCLEI_BIN | No | Path to Nuclei executable (if not in PATH) | |
| BOUNTYPROOF_REPORT_DIR | No | Local evidence directory | .bountyproof/reports |
| BOUNTYPROOF_VERIFY_TLS | No | Verify TLS certificates | true |
| BOUNTYPROOF_IMPORT_ROOT | No | Allowed root for HAR, OpenAPI, and Postman files | . |
| BOUNTYPROOF_ALLOWED_PORTS | No | Allowed destination ports | 443 |
| BOUNTYPROOF_ALLOW_PRIVATE | No | Allow non-public IP addresses for lab use | false |
| BOUNTYPROOF_MAX_IMPORT_BYTES | No | Maximum imported surface file size | 20000000 |
| BOUNTYPROOF_NUCLEI_RATE_LIMIT | No | Maximum Nuclei requests per second | 2 |
| BOUNTYPROOF_SECURITYTRAILS_API_KEY | No | Optional historical DNS lookup API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sessionA | FIRST TOOL. Ask the user for every field before creating an engagement session; this sends no traffic. |
| scope_checkB | Validate a URL against the active session's in-scope and out-of-scope rules without HTTP traffic. |
| preflight_targetB | Check friction before live testing: stability, latency, redirect, rate limit, and WAF/CDN hints. |
| discover_surfaceC | Use Katana at the session rate limit after scope and preflight gates pass. |
| scan_high_signalB | Run HTTP-only Nuclei high/critical templates under session scope, rules, and rate limit. |
| verify_findingB | Re-run one exact Nuclei template 2-3 times inside the same authorized session. |
| import_surfaceB | Import a local HAR/OpenAPI/Postman file; values are redacted and out-of-scope endpoints are rejected. |
| register_auth_profilesC | Register auth profile metadata and secret environment-variable names; actual credentials are never stored. |
| compare_authorizationB | Replay one imported GET as owner and 1-3 other profiles, twice, without changing IDs or request data. |
| find_origin_candidatesA | Find unverified origin IP candidates using in-scope DNS hints and optional historical DNS; sends no IP traffic. |
| verify_origin_candidateC | After a fresh user decision, compare one HTTPS edge response with one direct-IP response using the target SNI/Host. |
| get_reportC | Load a report only when it belongs to the active engagement session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct phase or aspect of security testing (e.g., session setup, scope validation, scanning, verification). There is no functional overlap that would confuse an agent.
Most tool names follow a clear verb_noun pattern (e.g., start_session, import_surface). Only 'scope_check' deviates slightly (noun_verb), but the convention is otherwise consistent.
With 12 tools, the set covers essential security testing actions without being excessive. Each tool serves a clear purpose, and the count feels well-scoped for the domain.
The workflow from session start to report retrieval is covered. Minor gaps exist (e.g., no explicit session termination or report listing), but core operations are present.