smb-cybersecurity-policy-kit vs ISMS Directory
smb-cybersecurity-policy-kit is a plugin bundle for AI coding tools published by DonteWong. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ISMS Directory is an MCP server published by ismsdirectory.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  smb-cybersecurity-policy-kit |  ISMS Directory |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.4.0 Downloads/month (npm): 146 Downloads/week (npm): 49 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 | smb-cybersecurity-policy-kit | ISMS Directory |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | 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 (ismsdirectory.com/api/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) | 6 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dontewong/claude-plugins-official | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
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 Classification, Remote Work Security) plus a policy-auditor agent that grades existing policies against NIST CSF 2.0. Built for SMBs, MSPs, and IT leaders who need defensible, audit-ready documentation without hiring a vCISO. Each policy is parameterized via XML variables (industry, size, risk profile, geography) so generated documents are tailored, not generic.
ISMS Directory
Read-only search of a curated directory of ISO 27001, SOC 2 and compliance services.
How to run each
smb-cybersecurity-policy-kit As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install smb-cybersecurity-policy-kit@claude-communityISMS Directory As a remote MCP server
claude mcp add --transport http isms-directory https://ismsdirectory.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ISMS Directory 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: smb-cybersecurity-policy-kit · What it can do: ISMS Directory · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.