MCP.Market

RTBlint MCP server

online · 100% uptime
by aleksUIX·io.github.aleksUIX/rtblint·v0.14.4·4 stars
No reviews yet

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

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

4 stars

Reviews

Write one

Nobody has reviewed RTBlint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

RTBlint tools (6)

write = sends, deletes, buys or posts
  • get_adcp_capabilitiesFree

    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.

  • list_openrtb_versionsFree

    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.

  • validate_artf_requestFree

    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.

  • validate_artf_responseFree

    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.

  • validate_bid_requestFree

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

  • validate_bid_responseFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 640ms20/20
  • Tool poisoning6 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How RTBlint compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,243 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
38 ms
faster than 94% of 30,027 servers
GitHub stars
4
more than 82% of 28,706 servers

What its tools let an agent do: 6 read

Release history: 4 versions in the registry since 2026-08-16, latest 2026-10-21, typically one every 11 days.

Install RTBlint in Claude Code, Cursor or VS Code

claude mcp add --transport http rtblint https://rtblint.org/mcp
Add to Cursor

What the publisher says

From the RTBlint repository's README, as published. We do not edit it. Read it on GitHub

RTBlint

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 (ext subtrees 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.adm content vs the declared bid.mtype (native JSON encoding, VAST/DAAST roots, double-encoded payloads)
  • Request/response cross-validation: with the originating request supplied, every bid's impid, mtype, adm markup, dealid, seat, and currency are checked against what the request actually offered
  • JSON dialect: spec JSON types flag fields such as imp.secure and regs.coppa as integers, while the IAB OpenRTB protobuf schema declares 28 of them bool. Either encoding is correct on its own transport and wrong on the other, so the caller declares which one it meant
  • Exchange profiles: documented protocol extras on top of the spec. --profile google-ab accepts at: 3 (FIXEDPRICE) and requires Imp.ext.billingid. --profile prebid-server requires each Imp to name a bidder or stored request and refuses wseat/bseat. --profile xandr requires ext.appnexus.sellermemberid and video ext.appnexus.context. --profile magnite requires xAPI identity fields (imp.ext.rp.zoneid, site/app ext.rp.siteid, publisher.ext.rp.account_id). Business policy stays out
  • Nested specs OpenRTB carries as strings or opaque ext: Native Ads 1.2 markup (imp.native.request and native bid.adm, including required-asset pairing), GPP header vs gppsid and TCF 2 shape, ${AUCTION} macros on billing and loss URLs, EID/SUA structure, SKAdNetwork ext.skadn

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

RTBlint: common questions

Is RTBlint MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the RTBlint safety report
How do I install RTBlint?
It runs remotely at rtblint.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does RTBlint need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is RTBlint maintained?
The last commit was 3 days ago (2026-11-02). The latest release is v0.14.4.
Is RTBlint up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of RTBlint?
Servers from other publishers that do the same job: Oh My Posh Validator MCP server.
How does RTBlint compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,243 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to RTBlint

Same job from other publishers: the closest match first, then the best rated.

  • Oh My Posh Validator
    Validate oh-my-posh configurations and segment snippets against the official schema.
    A

More from aleksUIX →