MCP Server
RTBlint
io.github.aleksUIX/rtblint
What this MCP does
Validates OpenRTB and ARTF bid requests and responses against IAB specifications and reports structured conformance issues.
Capabilities
Tools
6
tools
get_adcp_capabilities
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.
Read only
Idempotent
Input schema
{'type': 'object', 'title': 'GetAdcpCapabilitiesInput', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'ext': {'type': 'object', 'description': 'Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation.'}, 'context': {'type': 'object', 'description': 'Caller-supplied context object. Echoed back unchanged in the response.'}, '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.'}, '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.'}, '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.'}, '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."}}}
Output schema
{'type': 'object', 'required': ['status', 'adcp_version', 'supported_protocols'], 'properties': {'status': {'type': 'string'}, 'operator': {'type': 'object'}, 'adcp_version': {'type': 'string'}, 'supported_protocols': {'type': 'array', 'items': {'type': 'string'}}}}
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.
Read only
Idempotent
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
Output schema
{'type': 'object', 'required': ['versions'], 'properties': {'versions': {'type': 'array', 'items': {'type': 'string'}}}}
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. The carried payloads are protobuf JSON, so they are validated in that dialect.
Read only
Idempotent
Input schema
{'type': 'object', 'required': ['payload'], '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'}}}
Output schema
{'type': 'object', 'required': ['version', 'payload_type', 'valid', 'issues'], 'properties': {'valid': {'type': 'boolean'}, 'issues': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'severity', 'message'], 'properties': {'id': {'type': 'string', 'description': 'Stable finding id.'}, 'path': {'type': 'string', 'description': 'JSON path of the finding.'}, 'message': {'type': 'string'}, 'severity': {'enum': ['error', 'warning', 'info'], 'type': 'string'}}}}, 'version': {'type': 'string'}, 'payload_type': {'type': 'string'}}}
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. 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.
Read only
Idempotent
Input schema
{'type': 'object', 'required': ['payload', 'rtb_request'], 'properties': {'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.'}, 'payload': {'type': 'string', 'description': 'The ARTF RTBResponse 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'}, '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.'}}}
Output schema
{'type': 'object', 'required': ['version', 'payload_type', 'applied', 'valid', 'issues'], 'properties': {'valid': {'type': 'boolean'}, 'issues': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'severity', 'message'], 'properties': {'id': {'type': 'string', 'description': 'Stable finding id.'}, 'path': {'type': 'string', 'description': 'JSON path of the finding.'}, 'message': {'type': 'string'}, 'severity': {'enum': ['error', 'warning', 'info'], 'type': 'string'}}}}, 'applied': {'type': 'boolean'}, 'version': {'type': 'string'}, 'application': {'type': 'object'}, 'payload_type': {'type': 'string'}}}
validate_bid_request
Validate an OpenRTB 2.x bid request JSON payload against a tracked spec version. Returns structured issues with rule ids, severities, and JSON paths.
Read only
Idempotent
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['payload'], 'properties': {'dialect': {'enum': ['spec-json', 'proto-json'], 'type': 'string', '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.'}, 'payload': {'type': 'string', 'description': 'The OpenRTB bid request as a raw JSON string.'}, 'profile': {'enum': ['spec', 'google-ab', 'prebid-server', 'xandr', 'magnite'], 'type': 'string', '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.'}, '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'}}}
Output schema
{'type': 'object', 'required': ['version', 'payload_type', 'valid', 'issues'], 'properties': {'valid': {'type': 'boolean', 'description': 'True when the payload has zero spec errors.'}, 'issues': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'severity', 'message'], 'properties': {'id': {'type': 'string', 'description': 'Stable finding id.'}, 'path': {'type': 'string', 'description': 'JSON path of the finding.'}, 'message': {'type': 'string'}, 'severity': {'enum': ['error', 'warning', 'info'], 'type': 'string'}}}}, 'dialect': {'enum': ['spec-json', 'proto-json'], 'type': 'string'}, 'profile': {'enum': ['spec', 'google-ab', 'prebid-server', 'xandr', 'magnite'], 'type': 'string'}, 'version': {'type': 'string'}, 'payload_type': {'type': 'string'}, 'cross_validated': {'type': 'boolean'}}}
validate_bid_response
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.
Read only
Idempotent
Input schema
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['payload'], 'properties': {'dialect': {'enum': ['spec-json', 'proto-json'], 'type': 'string', '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.'}, 'payload': {'type': 'string', 'description': 'The OpenRTB bid response as a raw JSON string.'}, 'profile': {'enum': ['spec', 'google-ab', 'prebid-server', 'xandr', 'magnite'], 'type': 'string', '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.'}, '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'}, '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.'}}}
Output schema
{'type': 'object', 'required': ['version', 'payload_type', 'valid', 'issues'], 'properties': {'valid': {'type': 'boolean', 'description': 'True when the payload has zero spec errors.'}, 'issues': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'severity', 'message'], 'properties': {'id': {'type': 'string', 'description': 'Stable finding id.'}, 'path': {'type': 'string', 'description': 'JSON path of the finding.'}, 'message': {'type': 'string'}, 'severity': {'enum': ['error', 'warning', 'info'], 'type': 'string'}}}}, 'dialect': {'enum': ['spec-json', 'proto-json'], 'type': 'string'}, 'profile': {'enum': ['spec', 'google-ab', 'prebid-server', 'xandr', 'magnite'], 'type': 'string'}, 'version': {'type': 'string'}, 'payload_type': {'type': 'string'}, 'cross_validated': {'type': 'boolean'}}}
History
Recent tool changes
Added
get_adcp_capabilities
Sept. 17, 2026, 12:40 p.m.
Added
list_openrtb_versions
Sept. 17, 2026, 12:40 p.m.
Added
validate_artf_response
Sept. 17, 2026, 12:40 p.m.
Added
validate_artf_request
Sept. 17, 2026, 12:40 p.m.
Added
validate_bid_response
Sept. 17, 2026, 12:40 p.m.
Added
validate_bid_request
Sept. 17, 2026, 12:40 p.m.
Discover
Similar MCP servers
validoria-mcp
com.validoria/validoria-mcp
Runs continuous website, API, and webshop tests covering security, SEO, performance, accessibility, browser journeys, and inciden…
NanoTools
io.github.nanotools-x402/nanotools
Offers utility APIs alongside web search, scraping, browser rendering, screenshots, SERP data, and SEO audits.
Revternal
io.github.pipeworx-io/revternal
Provides AI visibility checks, brand and competitor monitoring, structured data research, llms.txt generation, and GitHub develop…
Technographics
io.github.pipeworx-io/technographics
Profiles the technologies used by websites and provides AI visibility, competitor presence, and llms.txt auditing tools.
Sitemap Stats
io.github.pipeworx-io/sitemap-stats
Reads website sitemaps and reports their structure and contents for site analysis.
tools
site.jiebang.www/tools
Provides file, JSON/YAML, XML/SQL, cron scheduling, text, image, QR, URL, and SEO utilities, including scheduled task management.
mcp-toolbelt
com.papacasper/mcp-toolbelt
Runs website and infrastructure checks covering DNS, SSL, security headers, ports, vulnerabilities, performance, SEO, email deliv…
agent-ready-kit
com.mudko/agent-ready-kit
Scans websites for AI-agent readiness, SEO, accessibility, and security issues, and generates deployment files, remediation guida…