RTBlint
io.github.aleksUIX/rtblintVersion 0.14.4Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core.
Status
Responds236 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:44 UTC
- Latency
- 236 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://rtblint.org/mcpResponds236 msNo sign-in
Claude Code
claude mcp add --transport http rtblint https://rtblint.org/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: rtblint
Remote MCP server URL: https://rtblint.org/mcpCursor
{
"mcpServers": {
"rtblint": {
"url": "https://rtblint.org/mcp"
}
}
}VS Code
code --add-mcp '{"name":"rtblint","type":"http","url":"https://rtblint.org/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
6 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_adcp_capabilitiesAdCP 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. | No | Yes | Yes | No |
list_openrtb_versionsList 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. | No | Yes | Yes | No |
validate_artf_requestValidate 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. | No | Yes | Yes | No |
validate_artf_responseValidate 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. | No | Yes | Yes | No |
validate_bid_requestValidate an OpenRTB 2.x bid request JSON payload against a tracked spec version. Returns structured issues with rule ids, severities, and JSON paths. | No | Yes | Yes | No |
validate_bid_responseValidate 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Oct 21, 2026
- Updated
- Oct 21, 2026
- Website
- Not given
- Categories
- Uncategorized
- GDPR
- Not declared