# RTBlint (remote · rtblint.org)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

- remote · `rtblint.org`: 70/100 (this document), [markdown](https://verifymcp.io/servers/aleksuix-rtblint/rtblint.md), [page](https://verifymcp.io/servers/aleksuix-rtblint/rtblint)

## Channel facts

- Endpoint: `https://rtblint.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.8.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-17.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

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

### Hermes

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

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-17 (score 70)

First indexed and scored.

## MCP tools (6)

### `validate_bid_request` (~308 tokens)

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 parameters:

- `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, required): 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…

Output parameters:

- `cross_validated` (boolean)
- `dialect` (string)
- `issues` (array)
- `payload_type` (string)
- `valid` (boolean): True when the payload has zero spec errors.
- `version` (string)

### `validate_bid_response` (~376 tokens)

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 parameters:

- `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, required): 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…

Output parameters:

- `cross_validated` (boolean)
- `dialect` (string)
- `issues` (array)
- `payload_type` (string)
- `valid` (boolean): True when the payload has zero spec errors.
- `version` (string)

### `validate_artf_request` (~251 tokens)

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 parameters:

- `payload` (string, required): 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…

Output parameters:

- `issues` (array)
- `payload_type` (string)
- `valid` (boolean)
- `version` (string)

### `validate_artf_response` (~367 tokens)

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 parameters:

- `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, required): The ARTF RTBResponse as a raw JSON string.
- `rtb_request` (string, required): 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…

Output parameters:

- `application` (object)
- `applied` (boolean)
- `issues` (array)
- `payload_type` (string)
- `valid` (boolean)
- `version` (string)

### `list_openrtb_versions` (~50 tokens)

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.

Output parameters:

- `versions` (array)

### `get_adcp_capabilities` (~334 tokens)

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 parameters:

- `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.

Output parameters:

- `adcp_version` (string)
- `operator` (object)
- `status` (string)
- `supported_protocols` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aleksuix-rtblint/rtblint#diagnostics

## Score history

- 2026-08-17: 70

## Links

- Remote endpoint: https://rtblint.org/mcp
- Repository: https://github.com/aleksUIX/rtblint
- Changelog RSS feed: https://verifymcp.io/servers/aleksuix-rtblint/rtblint.xml
- Changelog JSON feed: https://verifymcp.io/servers/aleksuix-rtblint/rtblint.json
- HTML version of this page: https://verifymcp.io/servers/aleksuix-rtblint/rtblint