_ registry / mcp http-sse · checked 4h ago

advertising-protocols-mcp

https://inktdlomgdqrsqaalpey.supabase.co

Registry code: 4678a62bd96b8611

api record

Reference tools for advertisingprotocols.com — a curated encyclopedia of 70+ ad tech standards (programmatic, video, identity, privacy, agentic AI) and the MCP servers that implement them. Use `search_protocols` to find protocols by keyword, `get_protocol` for full details, `list_mcp_servers` to see MCP servers implementing a given protocol, and `search_glossary` for plain-English ad tech definitions.

endpoint
https://inktdlomgdqrsqaalpey.supabase.co/functions/v1/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is advertising-protocols-mcp live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is advertising-protocols-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does advertising-protocols-mcp have?
4 tools: search_glossary, get_protocol, search_protocols, list_mcp_servers.
Is advertising-protocols-mcp 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.
reachable
live
uptime, 30 days
99.5%

90 days 99.4%· all time 99.4%

latency
1,410ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 334 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search ad tech protocols
  • get protocol details
  • look up ad tech terms
  • list mcp servers implementing a protocol
takes → gives
text → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

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.

  • list_mcp_servers reads open 12h ago

    List MCP servers in the AdvertisingProtocols directory. Optionally filter by protocol slug/label (e.g. 'adcp'), vendor, category, or 'officialOnly' to get only publisher-owned servers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1
        },
        "vendor": {
          "type": "string",
          "description": "Vendor name substring (e.g. 'Google', 'IAB')."
        },
        "protocol": {
          "type": "string",
          "description": "Protocol slug or label to filter by (e.g. 'adcp', 'AdCP', 'aamp')."
        },
        "officialOnly": {
          "type": "boolean",
          "default": false
        }
      }
    }
    arguments 24 lines
  • search_glossary reads unknown 27h ago

    Search the AdvertisingProtocols glossary of 130+ ad tech terms (DSP, SSP, RTB, TCF, etc.) and return plain-English definitions.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 8,
          "maximum": 25,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Term or keyword to search for."
        }
      }
    }
    arguments 19 lines
  • get_protocol reads unknown 12h ago

    Fetch details for one advertising protocol by its slug (e.g. 'openrtb-2', 'adcp', 'aamp', 'ucp'). Returns description, governance, evidence links, use cases, and dependencies.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Protocol slug, e.g. 'openrtb-2' or 'adcp'."
        }
      }
    }
    arguments 13 lines
  • search_protocols reads unknown 12h ago

    Search the AdvertisingProtocols catalog of 80+ ad tech standards (OpenRTB, VAST, AdCP, AAMP, UID2, ARTF, etc.) by keyword. Matches title, description, tags, and category.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Keyword(s) to match, e.g. 'agentic', 'video', 'identity'."
        }
      }
    }
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 4678a62bd96b8611.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4678a62bd96b8611/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/4678a62bd96b8611/badge.svg)](https://brick.blue/agent/4678a62bd96b8611?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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.

_ also on supabase.co 124 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

116 more sit on this domain. All of them.