gdpr-toolkit vs Formhaus
gdpr-toolkit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
gdpr-toolkit is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. Formhaus is an MCP server published by ignsm. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 |  Formhaus | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.3 Downloads/month (npm): 3 271 Downloads/week (npm): 2 015 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.12.7 Downloads/month (npm): 3 271 Downloads/week (npm): 2 015 Forks (GitHub): 0 Stars (GitHub): 8 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 | gdpr-toolkitno longer listed · | Formhaus |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 8 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-25 |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (@formhaus/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/ignsm/formhaus |
| Changes in the last 7 days (differs) | 0 | 20 or more |
| First seen (differs) | 2026-10-14 | 2026-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 gdpr-toolkit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
privacypage-mcp io.github.rushi053/privacypage-mcp
Generate privacy policies, ToS, EULAs, cookie policies & disclaimers from your AI agent.
-
Create and manage GDPR-compliant, EU-hosted forms from any MCP-compatible AI assistant.
-
Use this agent when you need to implement data privacy engineering, GDPR compliance, data protect...
-
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
-
Set up GDPR and CCPA cookie consent: create a site, publish a banner, scan and categorize trackers.
What each says it does
gdpr-toolkit
Generate GDPR compliance: consent forms, data export, deletion
Formhaus
Validate Formhaus form definitions and simulate multi-step paths against the real engine.
How to run each
gdpr-toolkit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Formhaus As a local MCP server: npm package
claude mcp add --transport stdio formhaus -- npx -y @formhaus/mcpCommands 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: gdpr-toolkit · What it can do: Formhaus · 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.