Home / MCP registry index / io.github.aleksUIX/vastlint
VASTlint
io.github.aleksUIX/vastlint in the official MCP registry.
Endpoint https://vastlint.org/mcp. Source: github.com/aleksUIX/vastlint.
The registry describes it as: Validate VAST, VMAP, and DAAST ad tags against IAB specs. 246 rules, pure Rust core.
We read its 15 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
validate_vast validate_vast_url inspect_vast list_rules explain_rule fix_vast get_adcp_capabilities list_content_standards create_content_standards get_content_standards update_content_standards delete_content_standards calibrate_content validate_content_delivery list_creatives
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-aleksuix-vastlint)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.