RTBlint

REMOTE · RTBLINT.ORG · SCANNED AUG 17

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

Available components

70 70 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security74

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability76

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1873 tokens (~234/item across 8 items; 6 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · rtblint.org

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http aleksuix-rtblint https://rtblint.org/mcp

# ~/.codex/config.toml

[mcp_servers.aleksuix-rtblint]
url = "https://rtblint.org/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aleksuix-rtblint": {
      "type": "remote",
      "url": "https://rtblint.org/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add aleksuix-rtblint --url https://rtblint.org/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  aleksuix-rtblint:
    url: "https://rtblint.org/mcp"

// mcp.json

{
  "mcpServers": {
    "aleksuix-rtblint": {
      "type": "http",
      "url": "https://rtblint.org/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

17 Aug 26 70

First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Aug 2026 · Probed https://rtblint.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=rtblint.org	CN=WE1,O=Google Trust Services,C=US	9 Jul 2026	7 Oct 2026	ECDSA 256	ECDSA-SHA256	14ae5ab6901c54570ea819c7f5d8d9ab
SANs: rtblint.org, *.rtblint.org
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of rtblint.org. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
org.	present	26974	8	Verified
rtblint.org.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://rtblint.org/mcp	Verified	200
http (plaintext)	http://rtblint.org/mcp	HTTPS enforced	301	https://rtblint.org/mcp

MCP tools · 6 exposed · ~1,686 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

get_adcp_capabilities ~334

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.

Input Output Examples

Name	Type	Req	Description
adcp_major_version	integer	–	Deprecated in favour of adcp_version. AdCP major version the caller's payloads conform to. When omitted, assumes the highest supported major.
adcp_version	string	–	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 om…
context	object	–	Caller-supplied context object. Echoed back unchanged in the response.
ext	object	–	Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation.
idempotency_key	string	–	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 unknow…
protocols	array	–	Filter which per-protocol capability blocks are returned. Does not narrow supported_protocols, which declares what the agent implements.

Name	Type	Req	Description
adcp_version	string	yes	–
operator	object	–	–
status	string	yes	–
supported_protocols	array	yes	–

No examples provided.

list_openrtb_versions ~50

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.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
versions	array	yes	–

No examples provided.

validate_artf_request ~251

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.

Input Output Examples

Name	Type	Req	Description
payload	string	yes	The ARTF RTBRequest envelope as a raw JSON string.
version	string	–	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-20250…

Name	Type	Req	Description
issues	array	yes	–
payload_type	string	yes	–
valid	boolean	yes	–
version	string	yes	–

No examples provided.

validate_artf_response ~367

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.

Input Output Examples

Name	Type	Req	Description
apply	boolean	–	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	string	yes	The ARTF RTBResponse as a raw JSON string.
rtb_request	string	yes	The ARTF RTBRequest envelope this response answers, as a raw JSON string. Required: a mutation is only meaningful relative to the auction it targets.
version	string	–	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-20250…

Name	Type	Req	Description
application	object	–	–
applied	boolean	yes	–
issues	array	yes	–
payload_type	string	yes	–
valid	boolean	yes	–
version	string	yes	–

No examples provided.

validate_bid_request ~308

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

Input Output Examples

Name	Type	Req	Description
dialect	string	–	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 fo…
payload	string	yes	The OpenRTB bid request as a raw JSON string.
version	string	–	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-20250…

Name	Type	Req	Description
cross_validated	boolean	–	–
dialect	string	–	–
issues	array	yes	–
payload_type	string	yes	–
valid	boolean	yes	True when the payload has zero spec errors.
version	string	yes	–

No examples provided.

validate_bid_response ~376

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.

Input Output Examples

Name	Type	Req	Description
bid_request	string	–	Optional: the originating OpenRTB bid request as a raw JSON string. When supplied, every bid is also cross-checked against the Imp it references.
dialect	string	–	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 fo…
payload	string	yes	The OpenRTB bid response as a raw JSON string.
version	string	–	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-20250…

Name	Type	Req	Description
cross_validated	boolean	–	–
dialect	string	–	–
issues	array	yes	–
payload_type	string	yes	–
valid	boolean	yes	True when the payload has zero spec errors.
version	string	yes	–

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

17 Aug 17 Aug