API Tools

rtblint.org

Validates OpenRTB bid request and response JSON payloads against versioned specs, and lists available versions.

1 endpoint6 known toolsFirst detected August 7, 2026Last detected September 24, 2026

ENDPOINT 1

https://rtblint.org/mcp

No auth detected

MCP server metadata

Name: rtblint
Version: 0.13.0

Capabilities

toolspromptsresources

Server instructions

OpenRTB 2.x and ARTF validation tools backed by rtblint-core. Call validate_bid_request on bid request JSON and validate_bid_response on bid response JSON; both return structured issues with rule ids, severities, and JSON paths. Pass dialect=proto-json for gRPC bidstream payloads. Pass profile=google-ab for Google Authorized Buyers extras (at=3, Imp.ext.billing_id), profile=prebid-server for Prebid Server /openrtb2/auction extras (bidder or stored request per Imp, no wseat/bseat), profile=xandr for Microsoft Monetize extras, or profile=magnite for Magnite xAPI identity fields. Pass the originating request as bid_request to validate_bid_response to cross-check impid, markup, deals, seats, and currency. Call validate_artf_request on an ARTF RTBRequest envelope, then validate_artf_response on the mutation set before proposing it; set apply=true to write the mutations and revalidate. Call list_openrtb_versions for tracked spec ids. Call get_adcp_capabilities first when wiring this server into an AdCP pipeline. Payloads sent to this hosted endpoint may be stored (identifiers stripped) to improve rules. Details: https://rtblint.org/privacy/. Use local rtblint-mcp over stdio if the payload must not leave the machine.

Known tools 6

validate_bid_request

Validate an OpenRTB 2.x bid request JSON payload against a tracked spec version.

Inferred read-only

validate_bid_response

Validate an OpenRTB 2.x bid response JSON payload against a tracked spec version.

Inferred read-only

validate_artf_request

Validate an ARTF (IAB Tech Lab Agentic Real Time Framework) RTBRequest envelope: required members, lifecycle and payload coherence, tmax plausibility, originator and applicable_intents enums, plus full OpenRTB validation of the bid request and bid response it carries.

Inferred read-only

validate_artf_response

Validate an ARTF RTBResponse mutation set against the RTBRequest it answers: envelope id echo, declared intent against applicable_intents, operation and payload coherence, and whether each semantic path (/imp/{id}, /imp/{id}/pmp/deals/{id}, /user/data/segment, /seatbid/{seat}/bid/{id}) resolves to something the auction actually carries.

Inferred read-only

list_openrtb_versions

List every OpenRTB version id this build can validate against, from 2.0 through the monthly 2.6 snapshots.

Inferred read-only

get_adcp_capabilities

AdCP protocol discovery.

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.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.

Indexed

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