PII Scanner vs Secrets Leak Audit
PII Scanner is no longer listed on any marketplace we read: these are its last known data, as of 2026‑11‑07.
PII Scanner is a plugin bundle for AI coding tools published by danielrosehill. No marketplace we read lists it any more. Secrets Leak Audit is an MCP server published by tylerscomic-lab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  Secrets Leak Audit | |
|---|---|---|
| Community marketplace danielrosehill/claude-code-plugins | Removed on 2026-11-07 Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 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
| Fact | PII Scannerno longer listed · | Secrets Leak Audit |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (secrets-leak-audit-mcp.mcpize.run/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) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/danielrosehill/claude-pii-scanner-plugin | github.com/tylerscomic-lab/secrets-leak-audit-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 h ago, requires authentication |
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 PII Scanner
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Check text for leaked credentials before an agent writes or commits it. Runs locally.
-
secret-scanner tools.knurl/secret-scanner
Scan configs, files, or text for leaked secrets and obvious misconfigurations. Nothing stored.
-
Find leaked API keys, tokens and passwords in pasted text, see which are live, get a clean copy.
-
Betterleaks Cloud - GitHub & S3 Secret Scanner
Betterleaks Cloud - GitHub Secret Scanner + Validator
-
env-secret-exposure-analyzer-mcp io.github.vola-trebla/env-secret-exposure-analyzer-mcp
Scans projects for secret exposure: leaked API keys, unprotected .env files, and secrets in logs.
-
Scan codebases for LLM/AI SDK usage, exposed API tokens, and hardcoded secrets.
What each says it does
PII Scanner
Scan files, directories, or git repositories for personally identifiable information — credentials (gitleaks), generic PII (Microsoft Presidio), and matches against a user-maintained personal PII inventory (names, addresses, family, IDs) stored locally.
Secrets Leak Audit
Scan text and git diffs for committed credentials using real vendor key formats plus entropy.
How to run each
PII Scanner
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Secrets Leak Audit As a remote MCP server
claude mcp add --transport http secrets-leak-audit-mcp https://secrets-leak-audit-mcp.mcpize.run/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Secrets Leak Audit 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: PII Scanner · What it can do: Secrets Leak Audit · 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.