VASTlint
Validates, inspects, and repairs VAST ad tags, including wrapper chains, SIMID, VMAP, and DAAST.
A wrapper chain that redirects five hops deep and dies on an HTTP media file renders as a blank slot. The player reports nothing useful and the impression is already gone.
What it does about it
Walk the whole chain, get a stable rule id and a fix for every finding, and auto-repair the deterministic ones.
Findings are structured, not prose. Every one carries a stable rule id you can suppress, track, or cite in a ticket, a severity, the exact location in the payload, and guidance on the fix. The same verdict comes back whether you called the CLI, the library, the browser build, or the MCP server.
Preprint, ResearchGate, April 2026. A 17 KB CTV tag validates in 350 microseconds, 0.35% of a 100 ms bid window; a 44 KB tag in 2.1 ms, inside a typical creative-selection budget.
Coverage
- Rule catalog. 132 VAST, 29 DAAST, 25 VMAP, 9 SIMID
- Rule provenance. Every rule cites its source: the VAST spec, the XSD, an RFC, an ISO list, or a documented revenue impact
- Beyond validation. Wrapper chain resolution, OMID verification checks, VPAID detection, and deterministic auto-fix
- Reach. Eleven distribution channels across six language ecosystems
Calling it from an agent
VASTlint exposes 14 tools over the Model Context Protocol, hosted over HTTP with no install and no account. See the MCP overview for wiring it into Claude Code, Cursor, or your own agent loop.
Use it without installing anything
VASTlint runs in the browser at vastlint.org, against the same engine as the CLI. No account and no key.
Where it fits
VASTlint grades one crossing in the delivery chain. The other two cover the crossings on either side of it: RTBlint and Pixellint. Same output contract, same license, so a team can adopt one and add the others without relearning anything.