Skip to main content
Glama
rapid7

Rapid7 Bulk Export MCP Server

Official
by rapid7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Rapid7 Bulk Export MCP Server

No user-submitted related servers found.

    Related Servers

    • Rapid7 Bulk Export MCP

      Cgisclair29
      A
      license
      A
      quality
      B
      maintenance
      Exports vulnerability and asset data from Rapid7 Command Platform via the Bulk Export API into a local DuckDB database, enabling AI assistants to run natural language queries and SQL analysis with sandboxed security.
      9
      MIT

    • tenable-mcp-server

      tarhou
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for Tenable Vulnerability Management and the Tenable One platform, enabling LLMs to query assets, vulnerabilities, scans, exposure metrics, attack paths, and more via natural language.
      MIT

    • Database Assistant MCP Server

      vinycoolguy2015
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only exploration and querying of PostgreSQL or MySQL databases via MCP, with schema discovery, safe SQL validation, natural language to SQL conversion, and CSV export.
      11
      1
      -

    • tenable-mcp

      nguyenthdat
      A
      license
      A
      quality
      C
      maintenance
      Exposes Tenable security operations as MCP tools for AI-powered security workflows, enabling asset, vulnerability, scan, plugin, and tag management via natural language.
      17
      MIT

    • MetaGraph-MCP

      midsane
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables enterprise AI agents to query governed data lineage, PII-aware schema documentation, and semantic metadata from SQL logs via MCP, with role-based access and vector search.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool maps to a distinct stage or concern: starting exports, checking status, downloading/loading, loading from Parquet, querying, inspecting metadata, listing, and purging. Even the two load-related tools are clearly separated by input source (existing Parquet vs. completed export).

    Naming Consistency5/5

    All tool names follow a consistent verb_rapid7_noun pattern in snake_case, e.g., start_rapid7_export, check_rapid7_export_status, get_rapid7_schema, purge_rapid7_data. The naming is uniform and predictable across the entire set.

    Tool Count5/5

    Nine tools is well-scoped for the export-to-query-to-cleanup lifecycle. Each tool serves a necessary function without redundancy or bloat.

    Completeness5/5

    The tool surface covers the full workflow: create export, monitor progress, download/load data, alternate local Parquet ingestion, schema/stats inspection, querying, listing prior exports, and purging data. There are no obvious dead ends or missing lifecycle steps.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources