_ registry / mcp streamable-http · checked 2h ago

url2ad

https://url2ad.app

Registry code: d46b6102f3dfe220

api record

URL2Ad turns a public web page into a 15-second animated video ad, built from what that page says and shows. Call create_ad once the user has given the page and their own e-mail address. Then give them the page link: the free watermarked video is ready there in a few minutes. Use get_ad_status to say where an ad stands, and never say it is ready without checking. If the user is waiting, call it with wait_seconds 45 until the status is no longer building: it usually takes about 4 minutes in all. Otherwise tell them the e-mail will let them know. Use request_change only when the user asks for a…

endpoint
https://url2ad.app/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 it live, free and safe measured by this hub
Is url2ad live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is url2ad free to use?
Yes — the hub reached it with no key and no payment.
What tools does url2ad have?
3 tools: create_ad, request_change, get_ad_status.
Is url2ad 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
100%

90 days 100%· all time 100%

latency
70ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • create_ad unknown never probed

    Starts building a free watermarked 15-second video ad from a public web page, in the language of that page. Use it when the user asks for a video ad for their site, product, app or store. The address must be the user's own, given by them in this conversation: never guess it or use someone else's. It receives the link by e-mail. Calling it again with the same page and address returns the same ad.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url",
        "email"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The public web page to make the ad from, e.g. https://example.com. Social network profiles do not work."
        },
        "email": {
          "type": "string",
          "description": "The user's own e-mail address, which receives the link to the video."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • request_change unknown never probed

    Rebuilds an existing ad with a change the user asked for, such as other wording, colors or images. It uses up one of the changes left, and one free change is included, so call it only when the user asked for this change, and pass their request as they said it. The new version takes a few minutes: follow it with get_ad_status.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ad_id",
        "change"
      ],
      "properties": {
        "ad_id": {
          "type": "string",
          "description": "The ad_id returned by create_ad."
        },
        "change": {
          "type": "string",
          "description": "What the user wants changed, in their words (3 to 1000 characters)."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_ad_status unknown 2h ago

    Returns the state of an ad started with create_ad: building, preview_ready, paid, failed or unavailable, with its page link, the changes left and the reason for a failure. Use it when the user asks whether their ad is ready, or before saying that it is. To wait for an ad being built, pass wait_seconds and call again while the status is building.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ad_id"
      ],
      "properties": {
        "ad_id": {
          "type": "string",
          "description": "The ad_id returned by create_ad."
        },
        "wait_seconds": {
          "type": "integer",
          "maximum": 45,
          "minimum": 0,
          "description": "Holds the answer up to this long, returning as soon as the ad stops building. Default 0: answer at once."
        }
      },
      "additionalProperties": false
    }
    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 d46b6102f3dfe220.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d46b6102f3dfe220/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/d46b6102f3dfe220/badge.svg)](https://brick.blue/agent/d46b6102f3dfe220?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
70%

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.