# Yaml Validator — REST API endpoint `yaml-validator`

Validate YAML and return either the re-formatted document or the parse error with its line and column. Valid input is re-emitted with the chosen indentation, optionally with keys sorted alphabetically at every level.

- Category: validation
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/yaml-validator/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/yaml-validator/
- Same tool on the other surface: https://findutils.com/mcp/yaml-validator/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/yaml-validator/execute \
  -H "Content-Type: application/json" \
  -d '{
    "yaml": "name: x\ntags:\n  - a\n  - b"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/yaml-validator
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `yaml` | string | yes | The YAML text to validate and format. |
| `indent` | integer | no | Indentation width for the formatted output (1-8). Default: 2. Default: `2`. |
| `sort_keys` | boolean | no | Sort mapping keys alphabetically at every level. Default: false. Default: `false`. |

Example arguments (verified):

```json
{
  "yaml": "name: x\ntags:\n  - a\n  - b"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:yaml_validator`. Full MCP reference: https://findutils.com/mcp/yaml-validator/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt