Payload Validator
Validate JSON, YAML, XML and CSV with exact line/column errors and silent-corruption warnings.
| Endpoint | https://payload-validator.gumballtools.com/api/mcp (streamable-http) |
|---|---|
| Registry version | 0.1.0 |
| Now | 5 tools · grade F (42) · pin ts_ef360da88ede51fea5c9078bc516a939 · protocol 2025-06-18 |
| First / last listed | 2026-11-06 01:11 UTC / 2026-11-06 01:11 UTC |
| Grade over time | 2026-11-06: F (42), 5 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: validate_json validate_yaml validate_xml validate_csv validate_auto
validate_json | Validates a JSON document and reports every problem with an exact line and column.
Use this whenever you need to know why a JSON payload is failing, or to check a JSON document you or a user produced before sending it somewhere that will reject it.
Do not do this by reading the JSON yourself. Three of the findings are invisible to inspection and to JSON.parse alike:
(1) Duplicate keys. `{"port": params: input* |
validate_yaml | Validates a YAML document, including the values that mean different things to different YAML loaders.
Use this for any YAML you are about to write or have just been given — CI configs, Kubernetes manifests, docker-compose files, OpenAPI specs, Ansible playbooks.
Do not reason about YAML type resolution yourself. It is the single most reliable way to be confidently wrong about a config file, beca params: input* |
validate_xml | Validates an XML document for well-formedness, namespace correctness, and the entity-based attacks that arrive as XML.
Use this before parsing XML you received, and when an XML document is being rejected by something that will not say why.
Do not eyeball this. Four classes of genuinely invalid XML are accepted by ordinary well-formedness checkers, so "it validated" does not mean what it appears params: input* |
validate_csv | Validates CSV text against RFC 4180 and reports ragged rows individually, with both field counts.
Use this before loading a CSV, and whenever a CSV-derived number looks wrong.
Do not attempt this by reading the file, and be aware that loading it successfully proves nothing. The failure that matters is the ragged row: a file where one row has six fields and the header has five loads without compl params: input*, delimiter, hasHeader |
validate_auto | Detects whether a payload is JSON, YAML, XML or CSV, then validates it.
Use this when you have a blob of text and do not know what it is — a file with no extension, a clipboard paste, a response body with an unhelpful content type, or a config file whose format you would otherwise have to guess.
Detection is structural and the reason is always returned, so the assumption is visible rather than h params: input* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.