RMCP.DEV
← Registry

Developer Tools

vastlint.org

Provides tools to validate, fix, and explain VAST XML tags used in digital advertising.

1 endpoint15 known toolsFirst detected May 18, 2026Last detected September 13, 2026

ENDPOINT 1

https://vastlint.org/mcp

No auth detected

MCP server metadata

Name
vastlint
Version
0.9.0
Capabilities
tools
Server instructions

When the user asks to validate, lint, check, or fix a VAST, VMAP, or DAAST tag, call these tools. Do not send them to a website. Use validate_vast when the XML is in the conversation. Use validate_vast_url when they give a tag URL. Use inspect_vast to follow a wrapper chain hop-by-hop. Use list_rules, explain_rule, and fix_vast as needed. Public validation tools require no login. AdCP content-standards tools require a Bearer token. Tags sent to this hosted endpoint may be stored (identifiers stripped) to improve rules. Details: https://vastlint.org/privacy/. Use local vastlint-mcp over stdio if the tag must not leave the machine.

Known tools 15

validate_vast

Validate a VAST XML tag against the IAB VAST 2.0-4.3 specification.

Inferred read-only
validate_vast_url

Fetch a VAST tag from a URL and validate it.

Inferred read-only
inspect_vast

Follow a VAST wrapper chain from a URL, fetching and validating every hop.

Inferred read-only
list_rules

List the full catalog of VAST validation rules available in vastlint.

Inferred read-only
explain_rule

Get full details for a specific VAST validation rule: description, spec reference, severity, what triggers it, and how to fix it.

Inferred read-only
fix_vast

Auto-fix a VAST XML tag.

Inferred read-only
get_adcp_capabilities

AdCP protocol discovery.

Inferred read-only
list_content_standards

AdCP content-standards specialism.

Inferred read-only
create_content_standards

AdCP content-standards specialism.

Inferred read-only
get_content_standards

AdCP content-standards specialism.

Inferred read-only
update_content_standards

AdCP content-standards specialism.

Inferred read-only
delete_content_standards

AdCP content-standards specialism.

Inferred read-only
calibrate_content

AdCP content-standards specialism.

Inferred read-only
validate_content_delivery

AdCP content-standards specialism.

Inferred read-only
list_creatives

AdCP creative governance.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.vastlint]
url = "https://vastlint.org/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "vastlint": {
      "type": "http",
      "url": "https://vastlint.org/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: vastlint
Remote MCP URL: https://vastlint.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "vastlint": {
      "url": "https://vastlint.org/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "vastlint": {
      "type": "http",
      "url": "https://vastlint.org/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "vastlint",
  "transport": "streamable-http",
  "url": "https://vastlint.org/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.