API Tools
rtblint.org
Validates OpenRTB bid request and response JSON payloads against versioned specs, and lists available versions.
ENDPOINT 1
https://rtblint.org/mcp
MCP server metadata
- Name
- rtblint
- Version
- 0.6.0
OpenRTB 2.x validation tools backed by rtblint-core. Use validate_bid_request to check a bid request JSON payload and validate_bid_response for a bid response; both return structured issues with rule ids, severities, and JSON paths, and accept an optional OpenRTB version id. Pass the originating request as bid_request to validate_bid_response to cross-check impid, markup, deals, seats, and currency. Use list_openrtb_versions to see the tracked versions.
Known tools 3
validate_bid_requestValidate an OpenRTB 2.x bid request JSON payload against a tracked spec version.
Inferred read-onlyvalidate_bid_responseValidate an OpenRTB 2.x bid response JSON payload against a tracked spec version.
Inferred read-onlylist_openrtb_versionsList every OpenRTB version id this build can validate against.
Inferred read-onlyCONNECT 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.rtblint]
url = "https://rtblint.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"rtblint": {
"type": "http",
"url": "https://rtblint.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: rtblint
Remote MCP URL: https://rtblint.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": {
"rtblint": {
"url": "https://rtblint.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"rtblint": {
"type": "http",
"url": "https://rtblint.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "rtblint",
"transport": "streamable-http",
"url": "https://rtblint.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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.