Ext Ops Panel
Open dashboard
Comparison

cybersecurity-policy-generator vs io.github.lennix1337/genexus

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. io.github.lennix1337/genexus is an MCP server published by lennix1337. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-06. 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

Where each is published
Marketplacecybersecurity-policy-generatorio.github.lennix1337/genexus
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: 2.0.4
Downloads/month (npm): 5 736
Downloads/week (npm): 2 194
Forks (GitHub): 28
Stars (GitHub): 42
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 4.3.1
Downloads/month (npm): 5 736
Downloads/week (npm): 2 194
Forks (GitHub): 28
Stars (GitHub): 42
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

cybersecurity-policy-generator vs io.github.lennix1337/genexus
Factcybersecurity-policy-generatorno longer listed · io.github.lennix1337/genexus
Marketplaces that list it (differs)02
Stars (GitHub) (differs)742
Forks (GitHub) (differs)028
Last release (differs)Not published2026-11-06
Where it runs (differs)Installs as a plugin bundleOn your machine (genexus-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/diegocconsolini/claudeskillcollectiongithub.com/lennix1337/genexus18mcp
Changes in the last 7 days (differs)03
First seen (differs)2026-10-162026-10-11

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.

  • smb-cybersecurity-policy-kit

    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…

    by DonteWong · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • Policyseed

    Draft SOC 2 policies from your AI assistant, via MCP

    by odedmoshe · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • iso27001-tanaji-hemant-naik

    Expert ISO 27001 compliance assistant for security and compliance teams. Use this skill whenever a user asks about ISO 27001 or ISO/IEC 27001, including any of the following: gap…

    by lawve-ai · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ISMS Copilot

    The compliance specialist your AI calls: ISO 27001, SOC 2, GDPR, NIS 2, DORA and more.

    by tristanroth1 · MCP server

    Listed on: Official MCP Registry · Describes a similar job

  • privacy-policy-generator-malik-taiar

    Guide for drafting privacy policies compliant with GDPR. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a privacy…

    by Malik Taiar · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a similar job

  • langguard-scope-mcp

    SCOPE - Security, Compliance & Operational Policy Evaluation - A Claude plugin that runs deterministic pre-flight compliance evaluation on agentic workflows. Maps every MCP tool…

    by LangGuard-AI · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes a similar job

Its card, with similar plugins by marketplace

What each says it does

cybersecurity-policy-generator

In its own words, on Community GitHub marketplaces:

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.

io.github.lennix1337/genexus

In its own words, on Official MCP Registry:

Read, edit, and analyze GeneXus 18 KB objects from Claude, Cursor, and AI agents.

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.

io.github.lennix1337/genexus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio genexus -- npx -y genexus-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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: io.github.lennix1337/genexus · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built