regexcronsql-validator
REMOTE · REGEXCRONSQL-VALIDATOR.ENCODARI.WORKERS.DEV · SCANNED OCT 5
Valida regex, cron y SQL contra ejecucion real. Pago por llamada via x402/USDC.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the regexcronsql-validator MCP server?
regexcronsql-validator is a hosted endpoint at https://regexcronsql-validator.encodari.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · regexcronsql-validator.encodari.workers.dev
claude mcp add --transport http encodi-regexcronsql-validator 'https://regexcronsql-validator.encodari.workers.dev/mcp'
{
"mcpServers": {
"encodi-regexcronsql-validator": {
"url": "https://regexcronsql-validator.encodari.workers.dev/mcp"
}
}
} {
"servers": {
"encodi-regexcronsql-validator": {
"type": "http",
"url": "https://regexcronsql-validator.encodari.workers.dev/mcp"
}
}
} [mcp_servers.encodi-regexcronsql-validator] url = "https://regexcronsql-validator.encodari.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"encodi-regexcronsql-validator": {
"type": "remote",
"url": "https://regexcronsql-validator.encodari.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add encodi-regexcronsql-validator --url 'https://regexcronsql-validator.encodari.workers.dev/mcp' --transport streamable-http
mcp_servers:
encodi-regexcronsql-validator:
url: "https://regexcronsql-validator.encodari.workers.dev/mcp" {
"McpServers": {
"encodi-regexcronsql-validator": {
"Transport": "http",
"Url": "https://regexcronsql-validator.encodari.workers.dev/mcp"
}
}
} assistant mcp add encodi-regexcronsql-validator -t streamable-http -u 'https://regexcronsql-validator.encodari.workers.dev/mcp'
{
"mcpServers": {
"encodi-regexcronsql-validator": {
"type": "http",
"url": "https://regexcronsql-validator.encodari.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Oct 2026 · Probed https://regexcronsql-validator.encodari.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=encodari.workers.dev | CN=WE1,O=Google Trust Services,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 674cb95b4a104ee10efee9f8b6684bb8 |
| SANs: encodari.workers.dev, *.encodari.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of regexcronsql-validator.encodari.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://regexcronsql-validator.encodari.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://regexcronsql-validator.encodari.workers.dev/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
validar_cron Validar expresión cron ~209
Calcula las próximas ejecuciones reales de una expresión cron usando cron-parser (no una suposición del modelo sobre cuándo dispararía). Interpreta los campos en UTC para que el resultado no dependa de la zona horaria del servidor que corre la tool. Cuesta $0.02 USDC (Base) por llamada.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Cantidad de próximas ejecuciones a devolver. Default 5, máximo 20. |
| cron_expression | string | yes | Expresión cron estándar de 5 campos (minuto hora día-mes mes día-semana), 6 con segundos, o un atajo como "@daily". Ej: "0 9 * * 1-5" = 9am de lunes a viernes. |
| from_date | string | – | Fecha ISO 8601 desde la cual calcular las próximas ejecuciones (ej: "2026-08-07T00:00:00Z"). Si se omite, se usa el momento actual. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | yes | Mensaje de error si valid_expression es false; null si es válida. |
| next_executions | array | yes | Fechas ISO 8601 en UTC de las próximas ejecuciones, en orden cronológico. |
| valid_expression | boolean | yes | false si la expresión cron no es válida. |
No examples provided.
validar_regex Validar expresión regular ~202
Ejecuta un patrón de expresión regular (motor nativo de JavaScript) contra una lista de strings de prueba y devuelve, para cada uno, si hizo match, el match completo y los grupos capturados. Usa RegExp real, no una suposición del modelo sobre qué haría el patrón. Cuesta $0.02 USDC (Base) por llamada.
| Name | Type | Req | Description |
|---|---|---|---|
| flags | string | – | Flags de RegExp de JavaScript a aplicar (ej: "gi" para global + case-insensitive). Vacío por defecto. |
| pattern | string | yes | El patrón de la expresión regular, sin delimitadores de barra (ej: "^[0-9]{3}-[0-9]{4}$", no "/^[0-9]{3}-[0-9]{4}$/"). |
| test_strings | array | yes | Lista de strings a evaluar contra el patrón, uno por uno. Máximo 50 strings, 2000 caracteres cada uno. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | yes | Mensaje de error si valid_pattern es false; null si es válido. |
| results | array | yes | Un resultado por cada test_string, en el mismo orden en que se recibieron. |
| valid_pattern | boolean | yes | false si el patrón no es una expresión regular válida en JS. |
No examples provided.
validar_sql Validar consulta SQL ~162
Ejecuta una consulta SQL (dialecto Postgres, motor pg-mem en memoria) contra tablas de prueba opcionales y devuelve las filas reales resultantes. Usa un motor SQL real, no una suposición del modelo sobre qué devolvería la query. Sin base de datos persistente: las tablas se crean desde cero en cada llamada y se descartan al terminar. Cuesta $0.04 USDC (Base) por llamada.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | La consulta SQL a ejecutar (ej: "SELECT nombre FROM clientes WHERE activo = true"). Máximo 5000 caracteres. |
| tables | array | – | Tablas de prueba a crear antes de correr la query. Omitir si la query no referencia ninguna tabla. Máximo 5 tablas. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | yes | Mensaje de error si valid_query es false; null si es válida. |
| rows | array | yes | Filas resultantes de la ejecución real de la query, hasta un máximo de 500. |
| truncated | boolean | yes | true si el resultado real tenía más de 500 filas y se cortó. |
| valid_query | boolean | yes | false si la query tiene un error de sintaxis o de ejecución (ej: tabla inexistente). |
No examples provided.
What is the regexcronsql-validator MCP server?
regexcronsql-validator is an MCP server listed in the public MCP registry as io.github.encodi/regexcronsql-validator. Valida regex, cron y SQL contra ejecucion real. Pago por llamada via x402/USDC. This page covers its hosted endpoint (https://regexcronsql-validator.encodari.workers.dev/mcp).
Is the regexcronsql-validator MCP server safe to use?
regexcronsql-validator scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the regexcronsql-validator MCP server expose?
regexcronsql-validator exposes 3 tools: validar_regex, validar_cron, validar_sql. Their descriptions and schemas cost roughly 573 tokens of context every time the server is loaded.
Does the regexcronsql-validator MCP server require authentication?
Its publisher declares no required credentials for regexcronsql-validator. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the regexcronsql-validator MCP server still maintained?
regexcronsql-validator is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.