# regexcronsql-validator (remote · regexcronsql-validator.encodari.workers.dev)

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

- Trust score: 63/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `regexcronsql-validator.encodari.workers.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/encodi-regexcronsql-validator/regexcronsql-validator.md), [page](https://verifymcp.io/servers/encodi-regexcronsql-validator/regexcronsql-validator)

## Channel facts

- Endpoint: `https://regexcronsql-validator.encodari.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http encodi-regexcronsql-validator https://regexcronsql-validator.encodari.workers.dev/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add encodi-regexcronsql-validator --url https://regexcronsql-validator.encodari.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  encodi-regexcronsql-validator:
    url: "https://regexcronsql-validator.encodari.workers.dev/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 63, +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.

### 2026-08-18 (score 62, +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.

### 2026-08-16 (score 61, +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.

### 2026-08-14 (score 60, +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.

### 2026-08-12 (score 59, +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.

### 2026-08-11 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 57)

First indexed and scored.

## MCP tools (3)

### `validar_regex` (~202 tokens)

Validar expresión regular

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.

Input parameters:

- `flags` (string): Flags de RegExp de JavaScript a aplicar (ej: "gi" para global + case-insensitive). Vacío por defecto.
- `pattern` (string, required): 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, required): Lista de strings a evaluar contra el patrón, uno por uno. Máximo 50 strings, 2000 caracteres cada uno.

Output parameters:

- `error`: Mensaje de error si valid_pattern es false; null si es válido.
- `results` (array): Un resultado por cada test_string, en el mismo orden en que se recibieron.
- `valid_pattern` (boolean): false si el patrón no es una expresión regular válida en JS.

### `validar_cron` (~209 tokens)

Validar expresión cron

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.

Input parameters:

- `count` (integer): Cantidad de próximas ejecuciones a devolver. Default 5, máximo 20.
- `cron_expression` (string, required): 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.

Output parameters:

- `error`: Mensaje de error si valid_expression es false; null si es válida.
- `next_executions` (array): Fechas ISO 8601 en UTC de las próximas ejecuciones, en orden cronológico.
- `valid_expression` (boolean): false si la expresión cron no es válida.

### `validar_sql` (~162 tokens)

Validar consulta SQL

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.

Input parameters:

- `query` (string, required): 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.

Output parameters:

- `error`: Mensaje de error si valid_query es false; null si es válida.
- `rows` (array): Filas resultantes de la ejecución real de la query, hasta un máximo de 500.
- `truncated` (boolean): true si el resultado real tenía más de 500 filas y se cortó.
- `valid_query` (boolean): false si la query tiene un error de sintaxis o de ejecución (ej: tabla inexistente).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/encodi-regexcronsql-validator/regexcronsql-validator#diagnostics

## Score history

- 2026-08-20: 63
- 2026-08-19: 62
- 2026-08-18: 62
- 2026-08-17: 61
- 2026-08-16: 61
- 2026-08-15: 60
- 2026-08-14: 60
- 2026-08-13: 59
- 2026-08-12: 59
- 2026-08-11: 58
- 2026-08-10: 57

## Links

- Remote endpoint: https://regexcronsql-validator.encodari.workers.dev/mcp
- Repository: https://github.com/encodi/regexcronsql-validator
- Changelog RSS feed: https://verifymcp.io/servers/encodi-regexcronsql-validator/regexcronsql-validator.xml
- Changelog JSON feed: https://verifymcp.io/servers/encodi-regexcronsql-validator/regexcronsql-validator.json
- HTML version of this page: https://verifymcp.io/servers/encodi-regexcronsql-validator/regexcronsql-validator