Rapid7 Bulk Export MCP Server
OfficialRelated Servers
Alternatives to Rapid7 Bulk Export MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceExports 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.9MIT

TernoDBI MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely explore and query connected databases and business tools through MCP, with access controls, semantic schema metadata, memory, and streaming or CSV export of large results.603 PyPI8Apache 2.0- AlicenseNot gradedqualityDmaintenanceAn 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.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Nessus vulnerability scans, analyze results, and generate reports through the MCP protocol.3MIT
- FlicenseAqualityDmaintenanceEnables 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.112-
- AlicenseAqualityCmaintenanceExposes Tenable security operations as MCP tools for AI-powered security workflows, enabling asset, vulnerability, scan, plugin, and tag management via natural language.17MIT
TDQS
Scored across 9 tools
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).
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.
Nine tools is well-scoped for the export-to-query-to-cleanup lifecycle. Each tool serves a necessary function without redundancy or bloat.
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.