MCP server for Intigriti bug bounty platform researcher API
Server has 8 tools with complete schemas and descriptions present. Naming follows verb_noun convention (list_, get_, create_, add_). However, descriptions are generic and lack LLM-optimization guidance. Parameter descriptions exist but are minimal (avg ~40 chars vs baseline 72). No output schemas documented. Error handling is absent, no recovery guidance, no actionable error messages. Missing parameter constraints (e.g., limit bounds, format specs). No tool annotations (readOnlyHint/destructiveHint). Composition is sound, tools are single-purpose and chainable via IDs.
Add a comment or update to an existing submission. Use this to respond to questions from the program team or provide additional information.
Submit a new bug report to a program. Include title, description, severity, proof of concept, and affected endpoint.
Get detailed information about a specific bug bounty program including scope, rewards, policy, response targets, and submission statistics.
Get the in-scope and out-of-scope assets (targets) for a specific program. Returns detailed scope information including endpoints, domains, and applications.
Get your researcher statistics including total submissions, acceptance rate, reputation score, and earnings.
No output schemas documented. LLMs cannot infer response structure, forcing them to guess what fields are returned and how to chain tools.
No error handling or recovery guidance. Errors are raw API responses with no actionable next steps for the LLM (e.g., 'API request failed: 404' tells agent nothing).
Missing parameter constraints. 'limit' in intigriti_list_submissions has no min/max bounds; LLM could pass 0 or 999999. 'severity' enum in create_submission lacks guidance on when to use each level.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | 2026-07-28+ | v2 |
Get detailed information about a specific bug submission including description, severity, status, and all communication.
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.
List your bug submissions across all programs or for a specific program. Filter by status, severity, or date range.
Descriptions are generic and lack LLM-optimization. 'Get detailed information about a specific bug bounty program...' (65 chars) does not explain WHEN to call this vs list_programs or get_program_scope. Baseline is 194 chars with context.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLM cannot distinguish safe read-only tools from destructive ones (create_submission, add_submission_comment) without explicit hints.