security-report-builder vs Re:port Flow MCP
security-report-builder is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
security-report-builder is a plugin bundle for AI coding tools published by Diego Consolini. No marketplace we read lists it any more. Re:port Flow MCP is an MCP server published by re-port-flow. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Re:port Flow MCP | |
|---|---|---|
| Community marketplace diegocconsolini/claudeskillcollection | Removed on 2026-10-22 Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 263 Downloads/week (npm): 21 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | security-report-builderno longer listed · | Re:port Flow MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 7 | 1 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.re-port-flow.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 0 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/diegocconsolini/claudeskillcollection | github.com/re-port-flow/reportflow-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (38 h ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of security-report-builder
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
hackenproof-all-reports-export
Export all reports of a HackenProof program into a structured file (Markdown, JSON, or CSV — user's choice)
-
Generate structured report handoff summaries for client teams
-
Turn an agent's findings into a clean web page: tables, charts, diagrams, one shareable link.
-
hackenproof-report-quality-scorer
Score a pasted vulnerability report on completeness and actionability before triage
-
Every KnowBe4 KMSAT reporting feature plus a local SQLite store that answers the cross-client
-
Generate structured incident reports and post-mortems
What each says it does
security-report-builder
Professional security report generator with HTML, PDF, and DOCX output. Transforms raw plugin-security-checker results into executive-ready reports with context-aware analysis reducing false positives by 85-90%. Features MITRE ATT&CK/ATLAS/OWASP/CWE framework mappings, customizable branding, and three report templates (Executive, Technical, Compliance). Includes unified version system and comprehensive severity adjustment rules.
Re:port Flow MCP
Generate PDF reports from Re:port Flow templates via Claude and other AI agents.
How to run each
security-report-builder
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Re:port Flow MCP As a remote MCP server
claude mcp add --transport http reportflow-mcp https://mcp.re-port-flow.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Re:port Flow MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of security-report-builder publish no settings it asks for, so we do not compare settings.
What it can do: security-report-builder · What it can do: Re:port Flow MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.