Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

regexcronsql-validator

REMOTE · REGEXCRONSQL-VALIDATOR.ENCODARI.WORKERS.DEV · SCANNED AUG 20

Valida regex, cron y SQL contra ejecucion real. Pago por llamada via x402/USDC.

+4 this week 63 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 573 tokens (~191/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · regexcronsql-validator.encodari.workers.dev

# add to Claude Code
claude mcp add --transport http encodi-regexcronsql-validator https://regexcronsql-validator.encodari.workers.dev/mcp
# ~/.codex/config.toml
[mcp_servers.encodi-regexcronsql-validator]
url = "https://regexcronsql-validator.encodari.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "encodi-regexcronsql-validator": {
      "type": "remote",
      "url": "https://regexcronsql-validator.encodari.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add encodi-regexcronsql-validator --url https://regexcronsql-validator.encodari.workers.dev/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  encodi-regexcronsql-validator:
    url: "https://regexcronsql-validator.encodari.workers.dev/mcp"
// mcp.json
{
  "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.

Changelog

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.

  • 20 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 +1
    • 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 57

    First indexed and scored.

Diagnostics

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 20 Aug 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
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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://regexcronsql-validator.encodari.workers.dev/mcp Verified 200
http (plaintext) http://regexcronsql-validator.encodari.workers.dev/mcp Inconclusive 405
MCP tools · 3 exposed · ~573 tokens

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.

Tool Tokens
validar_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.

NameTypeReqDescription
countintegerCantidad de próximas ejecuciones a devolver. Default 5, máximo 20.
cron_expressionstringyesExpresió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_datestringFecha ISO 8601 desde la cual calcular las próximas ejecuciones (ej: "2026-08-07T00:00:00Z"). Si se omite, se usa el momento actual.
NameTypeReqDescription
erroryesMensaje de error si valid_expression es false; null si es válida.
next_executionsarrayyesFechas ISO 8601 en UTC de las próximas ejecuciones, en orden cronológico.
valid_expressionbooleanyesfalse si la expresión cron no es válida.

No examples provided.

validar_regex ~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.

NameTypeReqDescription
flagsstringFlags de RegExp de JavaScript a aplicar (ej: "gi" para global + case-insensitive). Vacío por defecto.
patternstringyesEl 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_stringsarrayyesLista de strings a evaluar contra el patrón, uno por uno. Máximo 50 strings, 2000 caracteres cada uno.
NameTypeReqDescription
erroryesMensaje de error si valid_pattern es false; null si es válido.
resultsarrayyesUn resultado por cada test_string, en el mismo orden en que se recibieron.
valid_patternbooleanyesfalse si el patrón no es una expresión regular válida en JS.

No examples provided.

validar_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.

NameTypeReqDescription
querystringyesLa consulta SQL a ejecutar (ej: "SELECT nombre FROM clientes WHERE activo = true"). Máximo 5000 caracteres.
tablesarrayTablas de prueba a crear antes de correr la query. Omitir si la query no referencia ninguna tabla. Máximo 5 tablas.
NameTypeReqDescription
erroryesMensaje de error si valid_query es false; null si es válida.
rowsarrayyesFilas resultantes de la ejecución real de la query, hasta un máximo de 500.
truncatedbooleanyestrue si el resultado real tenía más de 500 filas y se cortó.
valid_querybooleanyesfalse si la query tiene un error de sintaxis o de ejecución (ej: tabla inexistente).

No examples provided.