Validate VAST, VMAP, and DAAST ad tags against IAB specs. 191 rules, pure Rust core.
Dev & Codev0.8.1ssevastlint.org repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 95ms |
| protocol | 8 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo vastlint@0.5.0 — registry declares deprecated 'sse' transport |
| tooling | 35 / 35 | tools/list OK: 14 tools e.g. "validate_vast"; 14/14 described, 14/14 fully-typed schemas, median description 266 chars |
| latency | 10 / 10 | initialize round-trip 95ms |
| provenance | 15 / 15 | description present; repository linked; version 0.8.1; namespace io.github.aleksUIX matches endpoint/repo |
Score 93/100 · latency 95ms · 14 tools · auth: open
Claude Code:
claude mcp add --transport http vastlint https://vastlint.org/mcp
Generic MCP client config:
{ "mcpServers": { "vastlint": { "type": "http", "url": "https://vastlint.org/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.aleksUIX/vastlint · referral link https://mcpqueen.com/go/io.github.aleksUIX/vastlint (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.aleksUIX/vastlint)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 21:16 | A | 93 | 95ms |