validate_content_delivery — VASTlint MCP Tool
validate_content_delivery
(validate content delivery) is one of 15 tools on the
VASTlint
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_content_delivery from your client
- Claude Code VASTlint validate_content_delivery run in your project directory
- Claude Desktop VASTlint validate_content_delivery ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VASTlint validate_content_delivery ~/.cursor/mcp.json
- VS Code VASTlint validate_content_delivery .vscode/mcp.json
- Zed VASTlint validate_content_delivery ~/.config/zed/settings.json
- Windsurf VASTlint validate_content_delivery ~/.codeium/windsurf/mcp_config.json
- Cline VASTlint validate_content_delivery ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VASTlint validate_content_delivery ~/.gemini/settings.json
- Grok VASTlint validate_content_delivery .mcp.json (in your project root)
- ChatGPT VASTlint validate_content_delivery Settings → Connectors → Advanced → Developer mode
- Claude.ai VASTlint validate_content_delivery Settings → Connectors → Add custom connector
- LangChain VASTlint validate_content_delivery pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport sse vastlint https://vastlint.org/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.