validate_openrtb — RTBlint MCP Prompt
validate_openrtb
is one of 2 prompts on the
RTBlint
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke validate_openrtb from your client
- Claude Code RTBlint Prompt/validate_openrtb run in your project directory
- Claude Desktop RTBlint Prompt/validate_openrtb ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor RTBlint Prompt/validate_openrtb ~/.cursor/mcp.json
- VS Code RTBlint Prompt/validate_openrtb .vscode/mcp.json
- Zed RTBlint Prompt/validate_openrtb ~/.config/zed/settings.json
- Windsurf RTBlint Prompt/validate_openrtb ~/.codeium/windsurf/mcp_config.json
- Cline RTBlint Prompt/validate_openrtb ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI RTBlint Prompt/validate_openrtb ~/.gemini/settings.json
- Grok RTBlint Prompt/validate_openrtb .mcp.json (in your project root)
- ChatGPT RTBlint Prompt/validate_openrtb Settings → Connectors → Advanced → Developer mode
- Claude.ai RTBlint Prompt/validate_openrtb Settings → Connectors → Add custom connector
- LangChain RTBlint Prompt/validate_openrtb pip install langchain-mcp-adapters
Other prompts on this server
RTBlint also offers 3 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.