rtblint

endpoint

https://rtblint.org/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is rtblint live?

Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.

Is rtblint free to use?

Yes — the hub reached it with no key and no payment.

What tools does rtblint have?

6 tools: validate_artf_request, validate_artf_response, validate_bid_request, validate_bid_response, get_adcp_capabilities, list_openrtb_versions.

Is rtblint safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_adcp_capabilities reads open 13h ago

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334

  {
    "type": "object",
    "title": "GetAdcpCapabilitiesInput",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "ext": {
        "type": "object",
        "description": "Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation."
      },
      "context": {
        "type": "object",
        "description": "Caller-supplied context object. Echoed back unchanged in the response."
      },
      "protocols": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Filter which per-protocol capability blocks are returned. Does not narrow supported_protocols, which declares what the agent implements."
      },
      "adcp_version": {
        "type": "string",
        "description": "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 omitted, the highest supported release is served."
      },
      "idempotency_key": {
        "type": "string",
        "description": "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 unknown field."
      },
      "adcp_major_version": {
        "type": "integer",
        "description": "Deprecated in favour of adcp_version. AdCP major version the caller's payloads conform to. When omitted, assumes the highest supported major."
      }
    }
  }

  arguments 34 lines copy
• list_openrtb_versions reads open 13h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• validate_artf_request reads unknown 4h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324

  {
    "type": "object",
    "required": [
      "payload"
    ],
    "properties": {
      "payload": {
        "type": "string",
        "description": "The ARTF RTBRequest envelope as a raw JSON string."
      },
      "version": {
        "type": "string",
        "description": "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-202501, 2.6-202505, 2.6-202606, 3.0"
      },
      "sample_kind": {
        "enum": [
          "submitted",
          "synthetic"
        ],
        "type": "string",
        "description": "Label test-generated payloads as synthetic in validation telemetry."
      }
    }
  }

  arguments 24 lines copy
• validate_artf_response reads unknown 4h ago

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233

  {
    "type": "object",
    "required": [
      "payload",
      "rtb_request"
    ],
    "properties": {
      "apply": {
        "type": "boolean",
        "description": "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": {
        "type": "string",
        "description": "The ARTF RTBResponse as a raw JSON string."
      },
      "version": {
        "type": "string",
        "description": "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-202501, 2.6-202505, 2.6-202606, 3.0"
      },
      "rtb_request": {
        "type": "string",
        "description": "The ARTF RTBRequest envelope this response answers, as a raw JSON string. Required: a mutation is only meaningful relative to the auction it targets."
      },
      "sample_kind": {
        "enum": [
          "submitted",
          "synthetic"
        ],
        "type": "string",
        "description": "Label test-generated payloads as synthetic in validation telemetry."
      }
    }
  }

  arguments 33 lines copy
• validate_bid_request reads unknown 13h ago

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

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "payload"
    ],
    "properties": {
      "dialect": {
        "enum": [
          "spec-json",
          "proto-json"
        ],
        "type": "string",
        "description": "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 follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration."
      },
      "payload": {
        "type": "string",
        "description": "The OpenRTB bid request as a raw JSON string."
      },
      "profile": {
        "enum": [
          "spec",
          "google-ab",
          "prebid-server",
          "xandr",
          "magnite",
          "dv360",
          "index-exchange",
          "index-exchange-seller",
          "unity",
          "vungle",
          "bidswitch",
          "bidswitch-supplier",
          "inmobi",
          "inmobi-supplier",
          "mobilefuse",
          "mobilefuse-sdk",
          "applovin-alx",
          "commerce-grid",
          "digital-turbine",
          "sovrn",
          "equativ",
          "equativ-supplier",
          "triplelift-supplier",
          "adform-handler",
          "yandex-sdk-bidding",
          "pubmatic-openwrap",
          "pubmatic-openwrap-ctv"
        ],
        "type": "string",
        "description": "Published vendor constraints on top of the selected spec. Choose the matching traffic direction. spec is the default. xandr targets Microsoft Monetize bidder traffic; magnite targets DV+ xAPI. Buyer, supplier and SDK profiles have distinct contracts. Optional extension fields remain optional unless the source explicitly requires them. A direction without a verified contract applies canonical checks and returns a scope warning."
      },
      "version": {
        "type": "string",
        "description": "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-202501, 2.6-202505, 2.6-202606, 3.0"
      },
      "sample_kind": {
        "enum": [
          "submitted",
          "synthetic"
        ],
        "type": "string",
        "description": "Label test-generated payloads as synthetic in validation telemetry."
      }
    }
  }

  arguments 66 lines copy
• validate_bid_response reads unknown 4h ago

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "payload"
    ],
    "properties": {
      "dialect": {
        "enum": [
          "spec-json",
          "proto-json"
        ],
        "type": "string",
        "description": "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 follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration."
      },
      "payload": {
        "type": "string",
        "description": "The OpenRTB bid response as a raw JSON string."
      },
      "profile": {
        "enum": [
          "spec",
          "google-ab",
          "prebid-server",
          "xandr",
          "magnite",
          "dv360",
          "index-exchange",
          "index-exchange-seller",
          "unity",
          "vungle",
          "bidswitch",
          "bidswitch-supplier",
          "inmobi",
          "inmobi-supplier",
          "mobilefuse",
          "mobilefuse-sdk",
          "applovin-alx",
          "commerce-grid",
          "digital-turbine",
          "sovrn",
          "equativ",
          "equativ-supplier",
          "triplelift-supplier",
          "adform-handler",
          "yandex-sdk-bidding",
          "pubmatic-openwrap",
          "pubmatic-openwrap-ctv"
        ],
        "type": "string",
        "description": "Published vendor constraints on top of the selected spec. Choose the matching traffic direction. spec is the default. xandr targets Microsoft Monetize bidder traffic; magnite targets DV+ xAPI. Buyer, supplier and SDK profiles have distinct contracts. Optional extension fields remain optional unless the source explicitly requires them. A direction without a verified contract applies canonical checks and returns a scope warning."
      },
      "version": {
        "type": "string",
        "description": "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-202501, 2.6-202505, 2.6-202606, 3.0"
      },
      "bid_request": {
        "type": "string",
        "description": "Optional: the originating OpenRTB bid request as a raw JSON string. When supplied, every bid is also cross-checked against the Imp it references."
      },
      "sample_kind": {
        "enum": [
          "submitted",
          "synthetic"
        ],
        "type": "string",
        "description": "Label test-generated payloads as synthetic in validation telemetry."
      }
    }
  }

  arguments 70 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.