RTBlint MCP server
Commit Nov 11, 2026Validates OpenRTB bid requests and responses against IAB Tech Lab specifications and exchange profiles.
Also known as aleksUIX/rtblint
- Stars
- 4
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.14.4
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
What is RTBlint MCP?
RTBlint validates OpenRTB bid requests and responses against IAB Tech Lab specifications and exchange profiles.
Summary generated from the project's README
About RTBlint MCP server
RTBlint provides specialized validation for OpenRTB bid requests and responses, ensuring they adhere to IAB Tech Lab specifications. It supports a wide range of versions from 2.0 through monthly 2.6 releases. Developers can use this server to check for malformed JSON, type mismatches, unknown fields, and semantic rule violations such as site and app exclusivity. It also handles complex checks like privacy signal contradictions and response markup coherence.
Users can connect via a hosted streamable HTTP endpoint or run a local version over stdio. The server includes tools for validating standard bid requests and responses, as well as specialized support for the Agentic Real Time Framework (ARTF). By providing optional dialect and profile arguments, users can validate against specific vendor contracts like Google Authorized Buyers, Prebid Server, Microsoft Monetize, or Magnite DV+ xAPI. This makes it a precise tool for ensuring programmatic advertising payloads meet strict exchange requirements.
What you can do with it
- 1Validate OpenRTB bid requestsCheck if a bid request JSON conforms to a specific OpenRTB version and contains all required fields.
- 2Perform cross-validation of responsesVerify that a bid response matches the specific parameters offered in the original originating request.
- 3Verify exchange profile complianceEnsure a payload adheres to the specific constraints and requirements of a particular advertising vendor.
Written from the project's README. Every use case is checked against a quote from it.
How to install RTBlint MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall RTBlint MCP in Claude Code
$ claude mcp add --transport http rtblint https://rtblint.org/mcpInstall RTBlint MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"rtblint": {
"url": "https://rtblint.org/mcp"
}
}
}Install RTBlint MCP in VS Code
.vscode/mcp.json
{
"servers": {
"rtblint": {
"type": "http",
"url": "https://rtblint.org/mcp"
}
}
}Install RTBlint MCP in VS Code CLI
$ code --add-mcp '{"name":"rtblint","type":"http","url":"https://rtblint.org/mcp"}'Install RTBlint MCP in Codex
$ codex mcp add rtblint --url https://rtblint.org/mcpInstall RTBlint MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.rtblint] url = "https://rtblint.org/mcp"
Install RTBlint MCP in Gemini CLI
$ gemini mcp add -s user --transport http rtblint https://rtblint.org/mcpInstall RTBlint MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"rtblint": {
"url": "https://rtblint.org/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablealeksuix/rtblint is public and reachablegithub.com/aleksuix/rtblint ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/aleksuix/rtblint ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 99 msPass
README
View on GitHubRTBlint
OpenRTB linter. Validates OpenRTB 2.x bid requests and bid responses against versioned IAB Tech Lab spec snapshots, from 2.0 through the monthly 2.6 releases (currently up to 2.6-202606).
Website and playground: rtblint.org
What it checks
- Malformed JSON and wrong top-level shape
- Required fields, including required non-empty arrays
- Unknown objects and fields per version catalog (
extsubtrees stay open) - Type mismatches (string, integer, float, boolean, object, and array forms)
- Documented enum values, including AdCOM lists and vendor ranges (500+)
- Deprecated, moved, removed, and not-yet-available fields across versions
- Semantic rules: site/app/dooh exclusivity, imp media type presence, skippable video dependencies, duration exclusivity, seatbid/nbr presence on responses, and more
- Response markup coherence:
bid.admcontent vs the declaredbid.mtype(native JSON encoding, VAST/DAAST roots, double-encoded payloads) - Request/response cross-validation: with the originating request supplied, every bid's
impid,mtype,admmarkup,dealid, seat, and currency are checked against what the request actually offered - JSON dialect: spec JSON types flag fields such as
imp.secureandregs.coppaas integers, while the IAB OpenRTB protobuf schema declares 28 of thembool. Either encoding is correct on its own transport and wrong on the other, so the caller declares which one it meant - Exchange profiles apply published request, response and paired constraints for the selected vendor and traffic direction. Optional extensions stay optional unless the source explicitly requires them. Profiles include Google Authorized Buyers, Prebid Server, Microsoft Monetize, Magnite DV+ xAPI and separate buyer, supplier and SDK contracts. See exchange profile evidence for sources, fixtures and limits
- Nested specs OpenRTB carries as strings or opaque
ext: Native Ads 1.2 markup (imp.native.requestand nativebid.adm, including required-asset pairing), GPP header vsgpp_sidand TCF 2 shape,${AUCTION_*}macros on billing and loss URLs, EID/SUA structure, SKAdNetworkext.skadn - Privacy signal contradictions:
regs.coppa/device.lmt/device.dnt/regs.gdprversus identifiers on the same payload, TCF Purpose 1 versus device-storage IDs, US Privacy Opt-Out Sale versus hashed EIDs, email-shapeduser.id/site.page, DSA Transparency field presence. Findings describe the document. They do not state a legal conclusion. - ARTF envelopes and mutation sets, including applying the mutations and revalidating what comes out
Every finding carries a stable rule id, a severity, a message, and a JSON path.
ARTF
ARTF, the IAB Tech Lab Agentic Real Time Framework, hands an agent an OpenRTB payload inside an RTBRequest envelope and takes back mutations: proposed changes the orchestrator may accept or reject one at a time. Nothing in the framework checks that the auction still validates once they are applied, and a mutation is only meaningful relative to the request it targets.
# The envelope, plus full OpenRTB validation of what it carries
rtblint validate --type artf-request rtb-request.json
# The mutation set against the auction it targets
rtblint validate --type artf-response --request rtb-request.json rtb-response.json
# Apply the mutations, revalidate, and report only what the mutations broke
rtblint validate --type artf-response --apply --request rtb-request.json rtb-response.json
Three passes:
- Envelope. Required members,
lifecycleagainst the payloads actually carried,tmaxplausibility for an in-auction call,originatorandapplicable_intentsenum values, and the carried bid request and bid response validated as protobuf JSON. - Mutations. The response id echoes the extension point request id (not the bid request id), each declared intent is in
applicable_intents, the operation and payload oneof member match the intent, and every semantic path (/imp/{id},/imp/{id}/pmp/deals/{id},/user/data/segment,/seatbid/{seat}/bid/{id}) resolves to something the auction carries.ADJUST_DEAL_MARGINis reported as having no OpenRTB field to write to, because it does not. - Applied. The mutations are written in and the result revalidated, reporting the OpenRTB findings the mutations introduced with pre-existing findings filtered out. What the agent broke, not what arrived broken.
The ARTF v1.0 document and its .proto use different vocabularies for the same mutation (activateSegments and a value: {IDsPayload: ...} wrapper against ACTIVATE_SEGMENTS and top-level oneof members). Payloads written from the document are mapped and reported as artf.mutation.legacy_spec_encoding rather than dismissed as unknown.
Surfaces
| Surface | Package | Status |
|---|---|---|
| Rust CLI | rtblint |
Working |
| Rust library | rtblint-core |
Working |
| MCP server | rtblint-mcp |
Working |
| Node (WASM) | rtblint-core on npm |
Working |
| GitHub Action | aleksUIX/rtblint |
Working |
| Python | rtblint on PyPI |
Not implemented yet |
| Go | github.com/aleksUIX/rtblint/go |
Not implemented yet |
OpenRTB 3.0 validates through its layered envelope: the transport objects (Openrtb, Request, Item, Deal, Source, Response, Seatbid, Bid) and the AdCOM 1.0 domain objects under item.spec (Placement), bid.media (Ad), and request.context. A 2.x payload sent to a 3.0 validator gets a migration diagnostic rather than a bare parse error. The 2.6-202204 snapshot has no extracted catalog and reports itself as unsupported instead of passing payloads silently. See ROADMAP.md for what's next and CHANGELOG.md for release history.
CLI
cargo install rtblint
rtblint validate request.json
rtblint validate --type response response.json
rtblint validate --type response --request request.json response.json
rtblint validate --version 2.5 --format json request.json
rtblint validate --dialect proto-json grpc-bid-request.json
rtblint validate --profile google-ab google-bid-request.json
rtblint validate --profile prebid-server pbs-auction.json
rtblint validate --profile xandr xandr-bid-request.json
rtblint validate --profile magnite magnite-bid-request.json
rtblint validate --resolve --cache ./supply-cache request.json
rtblint validate --summary bids.ndjson
rtblint validate --batch --summary bids.ndjson
cat request.json | rtblint validate --stdin
--request supplies the originating bid request for paired checks, including batch validation. --dialect proto-json selects the protobuf JSON encoding. --profile selects the vendor contract and traffic direction. Xandr checks bidder-facing Microsoft Monetize traffic; Magnite checks the DV+ xAPI extension model. Their optional seller, context and inventory identity fields are checked when supplied. Account-specific and runtime acceptance remain outside the payload. --resolve --cache <dir> checks SupplyChain hops against sellers.json and ads.txt / app-ads.txt from a local directory:
<dir>/sellers/<asi>/sellers.json
<dir>/ads/<site.domain>/ads.txt
<dir>/app-ads/<app.bundle>/app-ads.txt
Protobuf JSON also supports the IAB schema's native object alternatives:
imp.native.request_native (requestNative) and bid.adm_native
(admNative). Their native flags use booleans. The string alternatives
request and adm keep their JSON-encoded Native Ads markup. Supply one
alternative per oneof. Native assets remain validated and paired against
required request assets. See the IAB protobuf schema.
Nothing is fetched; populate the cache yourself. --batch lints one JSON object per line from a file or stdin. --summary adds rule-frequency totals for a captured stream (--summary bids.ndjson for the histogram alone). See ARTF for --type artf-request and --type artf-response.
Exit codes: 0 valid, 1 validation errors, 2 usage or I/O error.
GitHub Action
The Action lives in this repo. Pin a release tag so CI downloads that CLI tarball:
- uses: aleksUIX/rtblint@v0.13.0
with:
path: fixtures/bid-request.json
spec-version: 2.6-202505
version selects the CLI release (auto follows the action's own v* tag). spec-version is the OpenRTB snapshot. Linux and macOS runners, x86_64 and aarch64.
Node
import { validate, validateResponse, validateResponseAgainstRequest } from "rtblint-core";
const report = validate(JSON.stringify(bidRequest), "2.6-202505");
if (!report.valid) {
for (const issue of report.issues) {
console.log(`[${issue.severity}] ${issue.path}: ${issue.message} (${issue.id})`);
}
}
// Cross-validate a response against the request it answers.
const paired = validateResponseAgainstRequest(
JSON.stringify(bidResponse),
JSON.stringify(bidRequest)
);
For gRPC bidstream payloads and ARTF:
import {
validateDialect,
validateProfile,
validateArtfRequest,
validateArtfResponseApplied,
protoBoolDivergences,
} from "rtblint-core";
validateDialect(JSON.stringify(bidRequest), "proto-json");
validateProfile(JSON.stringify(bidRequest), "google-ab");
validateProfile(JSON.stringify(bidRequest), "prebid-server");
validateArtfRequest(JSON.stringify(rtbRequest));
// { result, application }: what the mutations broke, and the payloads they produced
const { result, application } = validateArtfResponseApplied(
JSON.stringify(rtbResponse),
JSON.stringify(rtbRequest)
);
protoBoolDivergences(); // the 28 fields the two schemas type differently
MCP server
Hosted Streamable HTTP (no install): https://rtblint.org/mcp. Smithery listing: aleksander/rtblint (same account as vastlint). Payloads sent to the hosted endpoint may be stored (identifiers stripped) so the rules can be improved; see rtblint.org/privacy. Local rtblint-mcp over stdio does not send payloads.
rtblint-mcp also speaks MCP over stdio. Tools: validate_bid_request, validate_bid_response (optional bid_request for cross-validation), validate_artf_request, validate_artf_response (apply writes the mutations and revalidates), list_openrtb_versions, get_adcp_capabilities. Validation tools take optional dialect and profile arguments.
The ARTF tools are the guardrail an agent calls around its own work: check the envelope it was handed, then check the mutation set it is about to propose, before the orchestrator sees it.
{
"mcpServers": {
"rtblint": { "url": "https://rtblint.org/mcp" }
}
}
Local stdio instead of the hosted endpoint:
{
"mcpServers": {
"rtblint": { "command": "rtblint-mcp" }
}
}
Rust library
use rtblint_core::{validate_bid_request_for_version, OpenRtbVersion};
let result = validate_bid_request_for_version(OpenRtbVersion::V2_6_202505, payload);
for issue in &result.issues {
println!("{} {} {:?}", issue.severity, issue.id, issue.path);
}
validate_bid_request_with_profile applies an exchange profile (Profile::GoogleAuthorizedBuyers, Profile::PrebidServer) on top of the spec. validate_bid_request_with_dialect selects spec JSON vs protobuf JSON.
Published profile IDs: spec, google-ab, prebid-server, xandr, magnite, dv360, index-exchange, index-exchange-seller, unity, vungle, bidswitch, bidswitch-supplier, inmobi, inmobi-supplier, mobilefuse, mobilefuse-sdk, applovin-alx, commerce-grid, digital-turbine, sovrn, equativ, equativ-supplier, triplelift-supplier, adform-handler, yandex-sdk-bidding, pubmatic-openwrap, pubmatic-openwrap-ctv. Select the matching direction, such as bidswitch for buyer 5.7 and bidswitch-supplier for supplier 1.1.
See the profile scope and source evidence for checked fields, supported directions and explicit gaps. Paired response validation uses the request as reference context; run request validation separately for its complete report.
JSON Schemas
schemas/ holds a JSON Schema (draft 2020-12) per tracked version, for both payload types, generated from the same catalogs the validator uses. IAB Tech Lab publishes no JSON Schema for 2.6 or 3.0, so these are the machine-readable contract for each monthly snapshot:
https://rtblint.org/schemas/openrtb-2.6-202606-bid-request.schema.json
https://rtblint.org/schemas/openrtb-2.6-202606-bid-response.schema.json
They cover structure, types, required fields, documented value sets, and AdCOM enum lists. What they cannot express is what the linter adds: deprecated and moved paths, version-specific removals, and the semantic rules. Validating against a schema is not the same as linting.
Regenerate after any catalog change (CI fails if they drift):
cargo run -p rtblint-core --example export_json_schemas
Documentation
Beyond this README, rtblint.org hosts the reference material:
- Diagnostic code reference: every stable issue id, each with a page covering what it means, why it matters, and how to fix it
- Versioned rule catalog: what every OpenRTB release added, deprecated, moved, or removed
- OpenRTB versions: a page per tracked version, 2.0 through 3.0
- Common OpenRTB mistakes and validating in CI
- Bid request anatomy, bid response anatomy, and the OpenRTB FAQ
Spec data and provenance
The validator runs on structured catalogs extracted from the IAB Tech Lab OpenRTB specifications: object names, field names, type notations, enumerated value sets, and section citations. The catalogs carry no spec prose. The dialect table is derived the same way, by comparing those catalogs against the field types the IAB OpenRTB protobuf schema declares. RTBlint is not affiliated with or endorsed by IAB Tech Lab. See NOTICE for attribution.
Supply chain
OpenSSF Scorecard runs weekly and publishes a public score. Dependabot covers Cargo, npm, and GitHub Actions. CodeQL scans Rust and JavaScript on every push and PR.
Three cargo-fuzz targets (validate, validate_response, validate_artf) run for 30 seconds each on every CI push. The validator must not panic on arbitrary input.
cargo +nightly fuzz run validate -- -max_total_time=60
License
Apache-2.0. See LICENSE and NOTICE.
Research
Sekowski, A. (2026). RTBLint: Executable, Versioned Contracts for OpenRTB Interoperability. Preprint. DOI · ResearchGate · PDF · Reproducibility artifact. Evaluates a frozen RTBLint 0.14.7 build, a context-matched reference checker, controlled Prebid Server replay and a separately archived research candidate with an explicit admission policy.
Sekowski, A. (2026). How Machine-Checkable Is OpenRTB? Classifying the Normative Content of the Protocol That Clears Real-Time Advertising. Preprint. DOI: 10.13140/RG.2.2.27937.57448
Sekowski, A. (2026). Measuring OpenRTB Dialects in Client-Side Header Bidding. Preprint. DOI: 10.13140/RG.2.2.26572.78720
Sekowski, A. (2026). Why CTV Ad Fraud Keeps Working: A Verifiability Analysis of the Connected TV Supply Chain. Preprint. ResearchGate. Field inventory extracted from this catalog. Artifacts: github.com/aleksUIX/ctv-verification-gap.
RTBlint MCP questions
How do I add RTBlint MCP to Claude Code?
Run claude mcp add --transport http rtblint https://rtblint.org/mcp in your terminal. Add --scope user to make it available in every project.
How do I add RTBlint MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What does RTBlint validate?
It validates OpenRTB 2.x bid requests and responses against versioned IAB Tech Lab spec snapshots, including malformed JSON, required fields, type mismatches, and semantic rules.
Can I validate a response against its originating request?
Yes, you can perform request/response cross-validation to check if bids match what the request actually offered.
Does the MCP server send my data to a remote endpoint?
The hosted Streamable HTTP endpoint may store payloads (with identifiers stripped) to improve rules, but the local stdio version does not send payloads.
What exchange profiles are supported?
Profiles include Google Authorized Buyers, Prebid Server, Microsoft Monetize, and Magnite DV+ xAPI.