RTBlint MCP Server

by aleksuix Your server? Claim it

answering

RTBlint is answering right now. Last checked 3 min ago. It exposes 6 tools. Last commit 26 Oct 2026.

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

Uptime history 79 days of history · worst day 91%

79 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

191 ms

Response time

average over 24h

Stars

last commit 26 Oct 2026

What changed 19

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 August 2026. No other catalogue keeps this.

21 Oct 4 tools changed the parameters they ask for validate_artf_request, validate_artf_response, validate_bid_request and 1 more

21 Oct a tool changed version2 times that day

10 Oct 2 tools changed the parameters they ask for validate_bid_request, validate_bid_response

10 Oct a tool changed version

30 Aug a tool changed version

18 Aug 2 tools changed the parameters they ask for4 times that day validate_bid_request, validate_bid_response

18 Aug a tool changed version2 times that day

17 Aug 2 tools changed the parameters they ask for validate_bid_request, validate_bid_response

17 Aug a tool changed version

and 4 more, back to 17 August 2026

What the code does

We read the source, 1 min ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command paper/openrtb-checkability/spec_examples.py:46, paper/openrtb-wild/analyze.py:34, paper/openrtb-wild/bestfit.py:43 и ещё 6

        r = subprocess.run(

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://rtblint.org/mcp

~/.codex/config.toml

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

.cursor/mcp.json

{
  "mcpServers": {
    "rtblint": {
      "url": "https://rtblint.org/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "rtblint": {
      "type": "http",
      "url": "https://rtblint.org/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

validate

validate_artf_request

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_response

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_request

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_response

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.

adcp

get_adcp_capabilities

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.

openrtb

list_openrtb_versions

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.

Endpoints

URL	Transport	State	Latency	Checked
https://rtblint.org/mcp	streamable-http	answering	87 ms	3 min ago

Alternatives to RTBlint

same job, measured the same way

VASTlint

by aleksuix

Validate VAST, VMAP, and DAAST ad tags against IAB specs. 246 rules, pure Rust core.

15 tools answering

Fin Codes API

by fincodesapi

Validate IBANs and bank codes, verify payee names, and screen names against sanctions lists.

answering

Openiban

by pipeworx-io

OpenIBAN MCP — validate an IBAN's checksum + bank code and resolve the bank name / BIC / city.…

353 installs/wk 46 tools answering

Physbound

by jonesrobm

Physical Layer Linter: validates RF and radar calculations against hard physical limits.

102 installs/wk local only

Agentsfile

by cloudcorprecords

Validate AGENTS.md and CLAUDE.md against repo reality: paths, scripts, and commands checked.

263 installs/wk local only

SpecPilot

by specpilot

Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent

2 tools answering

Lakelogic MCP

by lakelogic

Validate, lint, test-run and explain Open Lakehouse Contracts with LakeLogic, from any AI assistant.

790 installs/wk local only

VibeFix

by vibe-fixer

Free live-app check by an AI agent. On request it fixes the code and tests the app again.

7 tools answering

RTBlint — questions

Answers built from our own checks of this server.

What can RTBlint do?

It exposes 6 tools, read directly from the server on our last check. Among them: get_adcp_capabilities, list_openrtb_versions, validate_artf_request, validate_artf_response, validate_bid_request, validate_bid_response. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is RTBlint working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 191 ms. The bar chart above shows every period we have measured.

How do I connect RTBlint?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RTBlint need an API key?

No. RTBlint completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RTBlint?

It answers our handshake in 191 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is RTBlint open source?

The code is open source: it is published under the Apache-2.0 licence, written in Rust and 4 stars on GitHub. The licence covers the code in the repository, not the hosted service at rtblint.org, which runs on its operator's own terms.