RTBlint
Server Details
Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- aleksUIX/rtblint
- GitHub Stars
- 1
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each validate_* tool targets a distinct artifact (ARTF vs OpenRTB, request vs response) and the descriptions make the boundaries clear, though validate_artf_request partially subsumes OpenRTB validation, which could cause slight selection hesitation. The two discovery tools (get_adcp_capabilities vs list_openrtb_versions) are distinguishable but both read as 'setup' calls.
All six tools use a consistent snake_case verb_noun pattern (get_, list_, validate_) with predictable subject qualifiers (artf/bid, request/response). The pattern is uniform and readable across the set.
Six tools is well-scoped for a validation/linting server: two discovery helpers plus four targeted validators. No tool feels redundant or padded.
The surface covers discovery plus validation of OpenRTB and ARTF requests/responses, which is the core lifecycle for this linter. It is read-only by nature, so CRUD gaps don't apply, though there is no batch/aggregate validation entry point an agent might want.
Available Tools
6 toolsget_adcp_capabilitiesARead-onlyIdempotentInspect
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.
Inputs: ext, context, protocols, adcp_version, +2 more. Returns: status, operator, adcp_version, supported_protocols
list_openrtb_versionsARead-onlyIdempotentInspect
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.
Inputs: no named parameters. Returns: versions
validate_artf_requestARead-onlyIdempotentInspect
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.
Inputs: payload (required), version, sample_kind. Returns: valid, issues, version, payload_type
validate_artf_responseARead-onlyIdempotentInspect
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.
Inputs: payload (required), rtb_request (required), apply, version, +1 more. Returns: valid, issues, applied, version, +2 more
validate_bid_requestARead-onlyIdempotentInspect
Validate an OpenRTB 2.x bid request JSON payload against a tracked spec version. Returns structured issues with rule ids, severities, and JSON paths.
Inputs: payload (required), dialect, profile, version, +1 more. Returns: valid, issues, dialect, profile, +3 more
validate_bid_responseARead-onlyIdempotentInspect
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.
Inputs: payload (required), dialect, profile, version, +2 more. Returns: valid, issues, dialect, profile, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Related MCP Connectors
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
Validate JSON, YAML, XML and CSV with exact line/column errors and silent-corruption warnings.
Signed deterministic checks for supplied JSON invoices, OpenAPI API contracts and JSON events.
Deterministic, read-only JSON payload validation (bounded JSON Schema 2020-12 subset).
Related MCP Servers
- AlicenseAqualityAmaintenanceVAST validation MCP server that checks ad tags against IAB VAST specifications, returning structured JSON with rule IDs, XPath locations, and spec references.719Apache 2.0
- FlicenseNot gradedqualityDmaintenanceValidates OpenAPI documents, JSON Schemas, and JSON payloads. Also compares OpenAPI specs and displays breaking changes.-
- AlicenseAqualityBmaintenanceVerification for agent-produced artifacts: schema contract, emptiness, generation provenance and mandate authority. An MCP server (Model Context Protocol over Streamable HTTP) exposing verify_artifact, verify_artifact_batch and bridge_check tools. Deterministic, Ed25519-signed, verifiable offline.2Apache 2.0
- AlicenseAqualityCmaintenanceValidates AI-generated artifacts (JSON, API responses, SQL) against a contract and returns a verdict.135 npm2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.