Skip to content

URL2Ad

app.url2ad/url2adurl2ad.appstreamable-httpv1.1.0Scanned

Turn a web page into a 15-second animated video ad: free preview from a URL and an e-mail.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • create_adStarts building a free 15-second video ad preview from a public web page, in the language of that page.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "create_ad" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Starts building a free 15-second video ad preview 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 preview link by e-mail. Calling it again with the same page and address returns the same ad.

    Annotations the server declares

    • title: Create a video ad from a web page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • request_changeRebuilds an existing ad with a change the user asked for, such as other wording, colors or images.Reads text others writeNo findings

    Why it is in this group

    • The name "request_change" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 with a preview, 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.

    Annotations the server declares

    • title: Change a video ad
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_ad_statusReturns 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.No findings

    Why it is in this group

    • The name "get_ad_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check where a video ad stands
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http url2ad https://url2ad.app/mcp
claude mcp add --transport http url2ad https://url2ad.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__url2ad__get_ad_status"
    ],
    "ask": [
      "mcp__url2ad__create_ad",
      "mcp__url2ad__request_change"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as url2ad. Review it before you use it.

Capability tags behind 2 rules
  • mcp__url2ad__create_ad untrusted-input, outbound
  • mcp__url2ad__request_change untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/app.url2ad/url2ad/verify?hash=00998bc011a11ebf71912ec0763e7317f3a2dcfb2866cd45a5cd99fe86e082b6" | jq -e '.changed == false'

Pinned hash 00998bc011a1, from Nov 1, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/app.url2ad/url2ad/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for app.url2ad/url2ad
[![anlyon.dev](https://anlyon.dev/badge/app.url2ad/url2ad.svg)](https://anlyon.dev/servers/app.url2ad/url2ad)

Source: MCP Registry. Synced Nov 1, 2026, 00:17 UTC.