gdpr-toolkit vs ConsentStack
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. ConsentStack is an MCP server published by consentstack.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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 |  ConsentStack | |
|---|---|---|
| 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: 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 | gdpr-toolkitno longer listed · | ConsentStack |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (app.consentstack.io/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) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago, requires a key |
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.
-
privacy-notice-generator-oliver-schmidt-prietz
Draft GDPR-compliant privacy notices as .docx for any EU/EEA jurisdiction and audience. Supports five notice types (Website/App, Applicant, Employee, Business Partner, B2C…
-
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…
-
privacypage-mcp io.github.rushi053/privacypage-mcp
Generate privacy policies, ToS, EULAs, cookie policies & disclaimers from your AI agent.
-
cookie-policy-generator-malik-taiar
Guide for drafting cookie policies compliant with GDPR and the ePrivacy Directive. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting…
-
gdpr-compliance-tanaji-hemant-naik
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy…
-
Local read-only tools: French telemarketing consent, GDPR offshore checklist, cost per kept meeting
What each says it does
gdpr-toolkit
Generate GDPR compliance: consent forms, data export, deletion
ConsentStack
Set up GDPR and CCPA cookie consent: create a site, publish a banner, scan and categorize trackers.
How to run each
gdpr-toolkit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ConsentStack As a remote MCP server
claude mcp add --transport http cookie-consent https://app.consentstack.io/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ConsentStack 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: gdpr-toolkit · What it can do: ConsentStack · 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.