Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

Related Servers

Alternatives to Intigriti Researcher MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Intigriti by syncing programs, scopes, and rules of engagement, then provides tools to search and generate actionable attack briefings.
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables security researchers to interact with Intigriti's bug bounty platform through Claude Desktop, providing access to programs, scope, activities, and rules of engagement via natural language.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables bug bounty hunters to browse programs, inspect scope details, track scope changes over time, and receive personalized, recency-boosted program recommendations based on their skill profile.
      4
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and agents to search bug bounty programs, retrieve policies and scopes, and check targets against active scope across HackerOne, YesWeHack, and Intigriti using personal API credentials.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving public vulnerability reward program directory data across Bugcrowd, YesWeHack, and HackerOne, including bounty ranges, scope assets, launch dates, and wildcard eligibility.
      56 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to browse bug bounty programmes, work on reports, and help with triage using only user-approved permissions.
      33
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: browsing programs, reading program detail, reading activity, versioned scope/rules reads, and payouts. There is mild overlap because get_program already returns current rules and scope counts while get_rules_version and get_scope_version expose the same data for a specific version. The descriptions mostly clarify when to use the versioned getters, but the boundary is not perfectly sharp.

    Naming Consistency5/5

    All tool names follow a consistent snake_case list_/get_ verb_noun pattern. The domain nouns are predictable (program, program_activity, scope_version, rules_version, payouts). No mixed conventions or vague verbs are present.

    Tool Count5/5

    Six tools is well within the ideal range and each tool has a clear role in a focused research surface. The set avoids unnecessary breadth while covering discovery, detail, activity, versioned rules/scopes, and payouts.

    Completeness3/5

    The server covers program discovery, program details, activity, versioned scope/rules data, and personal payouts. However, a researcher workflow has notable gaps: there are no tools for submissions/reports, personal submission history, or report lifecycle actions. These omissions prevent end-to-end researcher coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues