Ext Ops Panel
Open dashboard
Comparison

personal-data-protection-skill vs Gridzen Verification

personal-data-protection-skill is a plugin bundle for AI coding tools published by AltByteSG. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Gridzen Verification is an MCP server published by gridzen.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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

Where each is published
Marketplacepersonal-data-protection-skillGridzen Verification
Claude Code: claude-plugins-community Listed
Version: 0.4.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.1
Forks (GitHub): 0
Stars (GitHub): 0
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

personal-data-protection-skill vs Gridzen Verification
Factpersonal-data-protection-skillGridzen Verification
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-12
Where it runs (differs)Installs as a plugin bundleRemote server (gridzen.ai/developers/mcp)
Transport (differs)Not statedStreamable HTTP
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/altbytesg/personal-data-protection-skillgithub.com/immurray/gridzen-developer-kit
Changes in the last 7 days (differs)05
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 41 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

personal-data-protection-skill

In its own words, on Claude Code: claude-plugins-community:

Build and maintain personal-data-protection-compliant applications for Southeast Asia. Tech-agnostic guidance covering Singapore PDPA 2012, Thailand PDPA B.E. 2562 (2019), and Indonesia UU PDP 27/2022 - organized by where in the stack each obligation lands, not by statute section number. Reference material, not legal advice.

Gridzen Verification

In its own words, on Official MCP Registry:

Country verification research, integration planning and synthetic tests. No live identity checks.

How to run each

personal-data-protection-skill As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install personal-data-protection-skill@claude-community

Gridzen Verification As a remote MCP server

Claude Code
claude mcp add --transport http verification https://gridzen.ai/developers/mcp

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

Only Gridzen Verification 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: personal-data-protection-skill · What it can do: Gridzen Verification · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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