MCP MeasureMCP Measure

index observed

RTBlint

Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
87%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~3,117Tokens (tool definitions)
~4.4 KBTypical response size
Significant attention impact (2.44% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "rtblint": {
      "url": "https://rtblint.org/mcp"
    }
  }
}

Remote endpoints

https://rtblint.org/mcpstreamable-http

What it can do

Tool inventory

Tools (6)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢validate_bid_request(payload, version, dialect, profile)

Validate an OpenRTB 2.x bid request JSON payload against a tracked spec version. Returns structured issues with rule ids, severities, and JSON paths.

Input Schema

{
  "type": "object",
  "properties": {
    "payload": {
      "type": "string",
      "description": "The OpenRTB bid request as a raw JSON string."
    },
    "version": {
      "type": "string",
      "description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
    },
    "dialect": {
      "type": "string",
      "enum": [
        "spec-json",
        "proto-json"
      ],
      "description": "JSON dialect the payload is written in. spec-json (default) types flag fields such as imp.secure, regs.coppa and pmp.private_auction as integers, the way the OpenRTB specification does. proto-json follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration."
    },
    "profile": {
      "type": "string",
      "enum": [
        "spec",
        "google-ab",
        "prebid-server",
        "xandr",
        "magnite"
      ],
      "description": "Exchange profile applied on top of the spec. spec (default) is the specification only. google-ab is Google Authorized Buyers OpenRTB: at=3 (FIXED_PRICE) is a valid auction type, and each Imp must carry ext.billing_id. prebid-server is Prebid Server /openrtb2/auction: each Imp must name a bidder or stored request, and wseat/bseat are refused. xandr is Microsoft Monetize outgoing requests: ext.appnexus.seller_member_id and video.ext.appnexus.context. magnite is Magnite xAPI identity fields: imp.ext.rp.zone_id, site/app ext.rp.site_id, publisher.ext.rp.account_id."
    }
  },
  "required": [
    "payload"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Output Schema

{
  "type": "object",
  "properties": {
    "version": {
      "type": "string"
    },
    "payload_type": {
      "type": "string"
    },
    "dialect": {
      "type": "string",
      "enum": [
        "spec-json",
        "proto-json"
      ]
    },
    "profile": {
      "type": "string",
      "enum": [
        "spec",
        "google-ab",
        "prebid-server",
        "xandr",
        "magnite"
      ]
    },
    "cross_validated": {
      "type": "boolean"
    },
    "valid": {
      "type": "boolean",
      "description": "True when the payload has zero spec errors."
    },
    "issues": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Stable finding id."
          },
          "severity": {
            "type": "string",
            "enum": [
              "error",
              "warning",
              "info"
            ]
          },
          "message": {
            "type": "string"
          },
          "path": {
            "type": "string",
            "description": "JSON path of the finding."
          }
        },
        "required": [
          "id",
          "severity",
          "message"
        ]
      }
    }
  },
  "required": [
    "version",
    "payload_type",
    "valid",
    "issues"
  ]
}
🟢validate_bid_response(payload, version, dialect, profile, bid_request)

Validate an OpenRTB 2.x bid response JSON payload against a tracked spec version. Optionally cross-validate it against the originating bid request (impid, mtype, adm markup, dealid, seat, and currency coherence). Returns structured issues with rule ids, severities, and JSON paths.

Input Schema

{
  "type": "object",
  "properties": {
    "payload": {
      "type": "string",
      "description": "The OpenRTB bid response as a raw JSON string."
    },
    "version": {
      "type": "string",
      "description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
    },
    "dialect": {
      "type": "string",
      "enum": [
        "spec-json",
        "proto-json"
      ],
      "description": "JSON dialect the payload is written in. spec-json (default) types flag fields such as imp.secure, regs.coppa and pmp.private_auction as integers, the way the OpenRTB specification does. proto-json follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration."
    },
    "profile": {
      "type": "string",
      "enum": [
        "spec",
        "google-ab",
        "prebid-server",
        "xandr",
        "magnite"
      ],
      "description": "Exchange profile applied on top of the spec. spec (default) is the specification only. google-ab is Google Authorized Buyers OpenRTB: at=3 (FIXED_PRICE) is a valid auction type, and each Imp must carry ext.billing_id. prebid-server is Prebid Server /openrtb2/auction: each Imp must name a bidder or stored request, and wseat/bseat are refused. xandr is Microsoft Monetize outgoing requests: ext.appnexus.seller_member_id and video.ext.appnexus.context. magnite is Magnite xAPI identity fields: imp.ext.rp.zone_id, site/app ext.rp.site_id, publisher.ext.rp.account_id."
    },
    "bid_request": {
      "type": "string",
      "description": "Optional: the originating OpenRTB bid request as a raw JSON string. When supplied, every bid is also cross-checked against the Imp it references."
    }
  },
  "required": [
    "payload"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Output Schema

{
  "type": "object",
  "properties": {
    "version": {
      "type": "string"
    },
    "payload_type": {
      "type": "string"
    },
    "dialect": {
      "type": "string",
      "enum": [
        "spec-json",
        "proto-json"
      ]
    },
    "profile": {
      "type": "string",
      "enum": [
        "spec",
        "google-ab",
        "prebid-server",
        "xandr",
        "magnite"
      ]
    },
    "cross_validated": {
      "type": "boolean"
    },
    "valid": {
      "type": "boolean",
      "description": "True when the payload has zero spec errors."
    },
    "issues": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Stable finding id."
          },
          "severity": {
            "type": "string",
            "enum": [
              "error",
              "warning",
              "info"
            ]
          },
          "message": {
            "type": "string"
          },
          "path": {
            "type": "string",
            "description": "JSON path of the finding."
          }
        },
        "required": [
          "id",
          "severity",
          "message"
        ]
      }
    }
  },
  "required": [
    "version",
    "payload_type",
    "valid",
    "issues"
  ]
}
🟢validate_artf_request(payload, version)

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. The carried payloads are protobuf JSON, so they are validated in that dialect.

Input Schema

{
  "type": "object",
  "properties": {
    "payload": {
      "type": "string",
      "description": "The ARTF RTBRequest envelope as a raw JSON string."
    },
    "version": {
      "type": "string",
      "description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
    }
  },
  "required": [
    "payload"
  ]
}

Output Schema

{
  "type": "object",
  "properties": {
    "version": {
      "type": "string"
    },
    "payload_type": {
      "type": "string"
    },
    "valid": {
      "type": "boolean"
    },
    "issues": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Stable finding id."
          },
          "severity": {
            "type": "string",
            "enum": [
              "error",
              "warning",
              "info"
            ]
          },
          "message": {
            "type": "string"
          },
          "path": {
            "type": "string",
            "description": "JSON path of the finding."
          }
        },
        "required": [
          "id",
          "severity",
          "message"
        ]
      }
    }
  },
  "required": [
    "version",
    "payload_type",
    "valid",
    "issues"
  ]
}
🟢validate_artf_response(payload, rtb_request, apply, version)

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. With apply=true the mutations are written into the payloads and revalidated, reporting the OpenRTB findings the mutations introduced. Call this before proposing mutations to an orchestrator.

Input Schema

{
  "type": "object",
  "properties": {
    "payload": {
      "type": "string",
      "description": "The ARTF RTBResponse as a raw JSON string."
    },
    "rtb_request": {
      "type": "string",
      "description": "The ARTF RTBRequest envelope this response answers, as a raw JSON string. Required: a mutation is only meaningful relative to the auction it targets."
    },
    "apply": {
      "type": "boolean",
      "description": "Apply the mutations and revalidate the result (default false). Returns the mutated payloads and the findings the mutations introduced, with pre-existing findings filtered out."
    },
    "version": {
      "type": "string",
      "description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
    }
  },
  "required": [
    "payload",
    "rtb_request"
  ]
}

Output Schema

{
  "type": "object",
  "properties": {
    "version": {
      "type": "string"
    },
    "payload_type": {
      "type": "string"
    },
    "applied": {
      "type": "boolean"
    },
    "valid": {
      "type": "boolean"
    },
    "issues": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Stable finding id."
          },
          "severity": {
            "type": "string",
            "enum": [
              "error",
              "warning",
              "info"
            ]
          },
          "message": {
            "type": "string"
          },
          "path": {
            "type": "string",
            "description": "JSON path of the finding."
          }
        },
        "required": [
          "id",
          "severity",
          "message"
        ]
      }
    },
    "application": {
      "type": "object"
    }
  },
  "required": [
    "version",
    "payload_type",
    "applied",
    "valid",
    "issues"
  ]
}
🟢list_openrtb_versions

List every OpenRTB version id this build can validate against, from 2.0 through the monthly 2.6 snapshots. Call this before pinning version on a validate_* tool.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Output Schema

{
  "type": "object",
  "properties": {
    "versions": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "versions"
  ]
}
🟢get_adcp_capabilities(adcp_version, adcp_major_version, protocols, context, idempotency_key, ...)

AdCP protocol discovery. Returns the AdCP releases this agent speaks and the bid-stream conformance metrics it computes. Call this first when wiring rtblint into an agentic buying pipeline: it declares the experimental measurement protocol and the metric ids (openrtb_error_count, openrtb_warning_count, openrtb_conformance_rate) that validate_bid_request and validate_bid_response produce. Part of the Ad Context Protocol (AdCP 3.1) specification.

Input Schema

{
  "type": "object",
  "properties": {
    "adcp_version": {
      "type": "string",
      "description": "Release-precision AdCP version the caller pins (for example \"3.1\"). When the pin is not in supported_versions the call returns a VERSION_UNSUPPORTED error naming the releases that would work. When omitted, the highest supported release is served."
    },
    "adcp_major_version": {
      "type": "integer",
      "description": "Deprecated in favour of adcp_version. AdCP major version the caller's payloads conform to. When omitted, assumes the highest supported major."
    },
    "protocols": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter which per-protocol capability blocks are returned. Does not narrow supported_protocols, which declares what the agent implements."
    },
    "context": {
      "type": "object",
      "description": "Caller-supplied context object. Echoed back unchanged in the response."
    },
    "idempotency_key": {
      "type": "string",
      "description": "AdCP 3.1 carries an idempotency key on every task request, reads included. This agent has no mutating surface and no replay store, so the key is accepted and ignored rather than rejected as an unknown field."
    },
    "ext": {
      "type": "object",
      "description": "Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation."
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "GetAdcpCapabilitiesInput"
}

Output Schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string"
    },
    "adcp_version": {
      "type": "string"
    },
    "operator": {
      "type": "object"
    },
    "supported_protocols": {
      "type": "array",
      "items": {
        "type": "string"
      }
    }
  },
  "required": [
    "status",
    "adcp_version",
    "supported_protocols"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded6 tools
verifiedversion not recorded6 tools
verifiedversion not recorded6 tools