Intigriti MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INTIGRITI_API_TOKEN | Yes | Your Intigriti API token with researcher permissions. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| intigriti_list_programsA | List all available bug bounty programs on Intigriti that you have access to as a researcher. Returns program details including name, company, status, and rewards. |
| intigriti_get_programA | Get detailed information about a specific bug bounty program including scope, rewards, policy, response targets, and submission statistics. |
| intigriti_get_program_scopeA | Get the in-scope and out-of-scope assets (targets) for a specific program. Returns detailed scope information including endpoints, domains, and applications. |
| intigriti_list_submissionsB | List your bug submissions across all programs or for a specific program. Filter by status, severity, or date range. |
| intigriti_get_submissionA | Get detailed information about a specific bug submission including description, severity, status, and all communication. |
| intigriti_create_submissionA | Submit a new bug report to a program. Include title, description, severity, proof of concept, and affected endpoint. |
| intigriti_add_submission_commentA | Add a comment or update to an existing submission. Use this to respond to questions from the program team or provide additional information. |
| intigriti_get_researcher_statsA | Get your researcher statistics including total submissions, acceptance rate, reputation score, and earnings. |
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 8 tools
Each tool has a clearly distinct purpose: listing vs getting programs, program vs scope, listing vs getting submissions, creating vs commenting, and stats. No overlapping functionality.
All tools follow the consistent pattern 'intigriti_verb_noun' (list_programs, get_program, get_program_scope, list_submissions, get_submission, create_submission, add_submission_comment, get_researcher_stats).
8 tools is well-scoped for a bug bounty server, covering both program discovery and submission management without unnecessary bloat or missing essentials.
The surface covers the full researcher workflow: browse programs, inspect program details and scope, list and view submissions, create submissions, and communicate via comments. No obvious gaps for the domain.