regex-permissions vs regexcronsql-validator
regex-permissions is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
regex-permissions is a plugin bundle for AI coding tools published by amehmeto. No marketplace we read lists it any more. regexcronsql-validator is an MCP server published by encodi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  regexcronsql-validator | |
|---|---|---|
| Community marketplace amehmeto/regex-permissions | Removed on 2026-10-15 Version: 0.10.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | regex-permissionsno longer listed · | regexcronsql-validator |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (regexcronsql-validator.encodari.workers.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/amehmeto/regex-permissions | github.com/encodi/regexcronsql-validator |
| 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 | Answered with HTTP 404 (4 days ago) |
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 regex-permissions
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Security guardrails for Claude Code. Intercepts every tool call via PreToolUse hook and evaluates it against your Open Agent Passport (OAP) policy before execution. Blocks…
-
Permission enforcement for Claude Code tool usage with policy-based rules, hierarchical settings, and optional kernel-enforced sandboxing via Landlock/seccomp (Linux) and Seatbelt…
-
Habblaud: permissões pelo escritório
Aprovar ou recusar pelo Habblaud os pedidos de permissão do Claude Code e responder as perguntas do agente (hook PermissionRequest).
-
A Claude Code plugin that warns or blocks prompts when the active Claude account doesn't match the expected account for the current directory. Useful for teams or individuals who…
-
PreToolUse Bash guard for Claude Code that still holds under --dangerously-skip-permissions. Blocks pipe-to-shell installs, disk wipes and fork bombs; asks before rm -rf…
-
Sync CLAUDE.md and the permissions allowlist, and refresh context on demand.
What each says it does
regex-permissions
Regex-based permission rules for Claude Code — collapse hundreds of literal allow/deny/ask rules into compact patterns
regexcronsql-validator
Valida regex, cron y SQL contra ejecucion real. Pago por llamada via x402/USDC.
How to run each
regex-permissions
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
regexcronsql-validator As a remote MCP server
claude mcp add --transport http regexcronsql-validator https://regexcronsql-validator.encodari.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only regexcronsql-validator 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: regex-permissions · What it can do: regexcronsql-validator · 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.