URL2Ad
REMOTE · URL2AD.APP
Turn a web page into a 15-second animated video ad: free preview from a URL and an e-mail.
Available components
Last scanned (21 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 545 tokens (~181/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://url2ad.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=url2ad.app | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | be6698a2ba6c99a40e7bdc2f48688643 |
| SANs: url2ad.app, www.url2ad.app, *.www.url2ad.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of url2ad.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| url2ad.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://url2ad.app/mcp | Verified | 200 | |
| http (plaintext) | http://url2ad.app/mcp | HTTPS enforced | 301 | https://url2ad.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_ad Create a video ad from a web page ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's own e-mail address, which receives the link to the video. | |
| url | string | yes | The public web page to make the ad from, e.g. https://example.com. Social network profiles do not work. |
| Name | Type | Req | Description |
|---|---|---|---|
| ad_id | string | yes | – |
| page_url | string | yes | Where the user watches the free watermarked video. |
| status | string | yes | – |
No examples provided.
get_ad_status Check where a video ad stands ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ad_id | string | yes | The ad_id returned by create_ad. |
| wait_seconds | integer | – | Holds the answer up to this long, returning as soon as the ad stops building. Default 0: answer at once. |
| Name | Type | Req | Description |
|---|---|---|---|
| ad_id | string | yes | The latest version of the ad. A change makes a new version. |
| changes_left | integer | yes | – |
| failure | string | – | Why the ad, or the last change to it, failed. |
| page_url | string | yes | – |
| status | string | yes | – |
No examples provided.
request_change Change a video ad ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ad_id | string | yes | The ad_id returned by create_ad. |
| change | string | yes | What the user wants changed, in their words (3 to 1000 characters). |
| Name | Type | Req | Description |
|---|---|---|---|
| ad_id | string | yes | The new version of the ad. |
| page_url | string | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the URL2Ad MCP server?
URL2Ad is a hosted endpoint at https://url2ad.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · url2ad.app
claude mcp add --transport http app-url2ad-url2ad 'https://url2ad.app/mcp'
What is the URL2Ad MCP server?
URL2Ad is an MCP server listed in the public MCP registry as app.url2ad/url2ad. Turn a web page into a 15-second animated video ad: free preview from a URL and an e-mail. This page covers its hosted endpoint (https://url2ad.app/mcp).
Is the URL2Ad MCP server safe to use?
URL2Ad scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the URL2Ad MCP server expose?
URL2Ad exposes 3 tools: create_ad, get_ad_status, request_change. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Does the URL2Ad MCP server require authentication?
No. We connected to URL2Ad without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the URL2Ad MCP server still maintained?
URL2Ad is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.