Vastlint
Validate IAB VAST 2.0–4.3 ad tags for spec compliance with 118 rules before you ship video or ad integrations.
Overview
vastlint is a MCP server for the Ship phase that validates IAB VAST 2.0–4.3 XML ad tags against 118 spec compliance rules.
What is this MCP server?
- 118-rule VAST XML validator covering IAB VAST 2.0 through 4.3
- Hosted SSE remote MCP at https://vastlint.org/mcp plus mcpb stdio bundle option
- Version 0.4.9 published with mcpb registry artifact
- Spec compliance focus for video ad tag pipelines
- 118 validation rules for IAB VAST XML
- Supports IAB VAST versions 2.0 through 4.3
- Server version 0.4.9 with SSE remote https://vastlint.org/mcp
Community signal: 13 GitHub stars.
What problem does it solve?
Shipping VAST creatives without automated linting risks player failures and IAB non-compliance discovered only after go-live.
Who is it for?
Indie ad-tech and video SaaS builders who need fast VAST 2.x–4.x validation inside Claude Code or Cursor.
Skip if: Products with no video advertising stack or teams that do not touch VAST XML.
What do I get? / Deliverables
After you connect the SSE or stdio MCP endpoint, your agent can run 118-rule VAST checks and return compliance issues before release.
- 118-rule compliance report for submitted VAST XML
- Actionable spec violation findings for IAB VAST 2.0–4.3
Recommended MCP Servers
Journey fit
How it compares
Specialized VAST XML validator MCP, not a general HTML linter or campaign analytics skill.
Common Questions / FAQ
Who is Vastlint for?
Developers and solo builders working on video ads, players, or SSP/DSP integrations who must enforce IAB VAST XML rules.
When should I use Vastlint?
Use it during ship testing whenever you change VAST tags, upgrade spec versions, or debug ad load errors.
How do I add Vastlint to my agent?
Add the remote SSE MCP URL https://Vastlint.org/mcp in your client, or install the v0.4.9 mcpb stdio package from the GitHub release per registry metadata.