cybersecurity-policy-generator vs com.screenata/compliance
cybersecurity-policy-generator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
cybersecurity-policy-generator is a plugin bundle for AI coding tools published by Diego Consolini. No marketplace we read lists it any more. com.screenata/compliance is an MCP server published by screenata.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  com.screenata/compliance | |
|---|---|---|
| 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.0.0 No figure published 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 | cybersecurity-policy-generatorno longer listed · | com.screenata/compliance |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 7 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.screenata.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/diegocconsolini/claudeskillcollection | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 43 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 cybersecurity-policy-generator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Generate NIST CSF 2.0-aligned cybersecurity policies for small and mid-size businesses. Five production-ready generators (Acceptable Use, Incident Response, Password & MFA, Data…
-
Draft SOC 2 policies from your AI assistant, via MCP
-
The compliance specialist your AI calls: ISO 27001, SOC 2, GDPR, NIS 2, DORA and more.
-
SCOPE - Security, Compliance & Operational Policy Evaluation - A Claude plugin that runs deterministic pre-flight compliance evaluation on agentic workflows. Maps every MCP tool…
-
HR policy documentation, legal compliance templates (GDPR/SOC2/HIPAA), employment contracts, and regulatory documentation
-
HR policy documentation, legal compliance templates (GDPR/SOC2/HIPAA), employment contracts, and regulatory documentation
What each says it does
cybersecurity-policy-generator
Professional cybersecurity policy document generator using 51 industry-standard templates from SANS and CIS Controls. Creates complete, framework-compliant policy documents (Markdown, Word, HTML, PDF) customized for your organization. Covers 15 security categories with mappings to ISO 27001, SOC 2, NIST CSF, CIS Controls v8, and GDPR.
com.screenata/compliance
Manage compliance controls, policies, and audit readiness for SOC 2, HIPAA, ISO 27001 and more.
How to run each
cybersecurity-policy-generator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.screenata/compliance As a remote MCP server
claude mcp add --transport http compliance https://api.screenata.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.screenata/compliance 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
Neither one's marketplaces publish the settings it asks for.
What it can do: cybersecurity-policy-generator · What it can do: com.screenata/compliance · 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.