Skip to main content
Glama
Cgisclair29

Rapid7 Bulk Export MCP

by Cgisclair29

Related Servers

Alternatives to Rapid7 Bulk Export MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI-powered analysis of Rapid7 vulnerability and asset data by exporting via the Bulk Export API and making it queryable through natural language or SQL in MCP-compatible tools.
      9
      31
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to HackerOne to pull bug bounty history, program scopes, and report details into a local SQLite database, exposing tools for searching, analyzing, and generating attack briefings using both personal and public disclosed reports.
      355
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Provides conversational access to a local CVE (Common Vulnerabilities and Exposures) database, enabling natural language queries to search vulnerabilities, retrieve detailed CVE information, and view security statistics.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A unified MCP server for Rapid7's security platform, exposing InsightVM (vulnerability management), InsightIDR (SIEM/investigations), and Metasploit Pro (pentest telemetry) as tools for Claude, Cursor, and any MCP-compatible LLM client.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Aggregates security intelligence feeds (vulnerabilities, news, threat intel) into a local SQLite database and provides MCP tools for AI agents to query and analyze them.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-assisted vulnerability management by connecting Claude Desktop to local Nessus and Tenable Vulnerability Management, allowing natural-language queries for scan management, threat intelligence enrichment, and prioritized remediation planning.
      -

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool covers a distinct phase of the export/query lifecycle: starting, checking, downloading, loading, listing, querying, inspecting, and purging. While list_rapid7_exports and check_rapid7_export_status both surface status information, their purposes are clearly separated and their descriptions remove ambiguity.

    Naming Consistency5/5

    Tool names consistently follow a verb_rapid7_object pattern, such as start_rapid7_export, download_rapid7_export, and get_rapid7_schema. Even query_rapid7 fits the pattern by treating Rapid7 as the object, and pluralization is used sensibly for list_rapid7_exports.

    Tool Count5/5

    Nine tools is well-scoped for the server's purpose: managing Rapid7 exports, loading data, and querying the local database. Each tool earns its place and there is no redundant bloat.

    Completeness5/5

    The tool set covers the complete export-to-analysis lifecycle: start an export, check status, download it, load existing Parquet files, list available exports, inspect schema and stats, query the data, and purge everything when done. No critical workflow dead-ends are apparent.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues