Ad Radar
REMOTE · APP.AD-RADAR.DEV
Search winning Meta ads with $50k+ in estimated spend, read hooks and scripts, and draft briefs.
Available components
Last scanned (20 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 21 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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1059 tokens (~176/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://app.ad-radar.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.ad-radar.dev | CN=YR1,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 2048 | SHA256-RSA | 643d51ad8b1c7bff2f10e0c67858b7ae3d9 |
| SANs: app.ad-radar.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of app.ad-radar.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| ad-radar.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Ad Radar", resource_metadata="https://app.ad-radar.dev/.well-known/oauth-protected-resource/api/mcp", scope="mcp:read"
Bearer realm="Ad Radar", resource_metadata="https://app.ad-radar.dev/.well-known/oauth-protected-resource/api/mcp", scope="mcp:read" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.clarity.ms https://*.clarity.ms https://c.bing.com; style-src 'self' 'unsafe-inline'; img-src 'self' https://fbcdn.net https://*.fbcdn.net https://fbsbx.com https://*.fbsbx.com data: blob: https://www.clarity.ms https://*.clarity.ms https://c.bing.com; media-src 'self' https://fbcdn.net https://*.fbcdn.net https://fbsbx.com https://*.fbsbx.com blob:; font-src 'self' data:; connect-src 'self' https://www.clarity.ms https://*.clarity.ms https://c.bing.com; frame-src 'none'; worker-src 'self' blob:; manifest-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://app.ad-radar.dev/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://app.ad-radar.dev/api/mcp |
| Authorisation server | https://app.ad-radar.dev |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.ad-radar.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://app.ad-radar.dev/api/mcp | HTTPS enforced | 308 | https://app.ad-radar.dev/api/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 →
advertiser_hooks Advertiser hooks ~59
Returns the hooks, hook mechanisms and angles an advertiser uses most, counted over all of its ads in the library. advertiserId is the advertiser id shown in search_ads rows.
| Name | Type | Req | Description |
|---|---|---|---|
| advertiserId | integer | yes | Advertiser id from a search_ads row |
No output schema declared.
No examples provided.
get_ad Ad details ~186
Returns the full record of one ad: headline, body, CTA, full transcript, metrics, spendEstimate (an ESTIMATE based on engagement, not real spend; spendLowerBound = it is a minimum, "at least"), delivery status, winnerObservation (when we first observed it above $50k), media (public URLs), links (post, Ad Library, landing page, board), tags (the same dimension and slug search_ads shows), publisher platforms and landing domain. The transcript is in English: when the ad runs in another language (e.g. Spanish), transcript is the English translation, translatedFrom names the language and transcriptOriginal holds the original script. Text fields are null when they aren't available for that ad; the links always point to the original.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | adKey ("meta:<id>"), a bare id or a Meta Ad Library id |
No output schema declared.
No examples provided.
get_swipe_prompt Swipe prompt ~230
Returns a prompt template built from one ad, written for the user to run on their own product. The result is JSON with the template text in the template field. kind='swipe' is a template that maps the ad's beats, checks the fit with the user's product, drafts a full version with the same structure and adds alternative hooks. kind='analysis' is a template that breaks down why the ad works (audience, funnel, psychology, weak spots) and how its structure applies to a business. product and niche are written into the template; without product the template keeps a placeholder for it.
| Name | Type | Req | Description |
|---|---|---|---|
| annotate | boolean | – | Mark the copy blocks inside the script when available (swipe only) |
| key | string | yes | adKey ("meta:<id>"), a bare id or a Meta Ad Library id |
| kind | string | – | swipe = rebuild the ad for another product; analysis = why the ad works |
| niche | string | – | Angle or audience for the template (swipe only) |
| product | string | – | The user's product, written into the template |
No output schema declared.
No examples provided.
list_taxonomy Taxonomy ~54
Lists the taxonomy dimensions of the Ad Radar library (awareness, angle, hook_pattern, vformat, pformat, landing...) with their valid values. These slugs are the values the tags filter of search_ads accepts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_ads Search ads ~431
Searches the Ad Radar library of Facebook and Instagram ads from the Meta Ad Library (every ad has at least $50k estimated spend), with the same filters as the Ad Radar board. By default it returns only active ads, sorted by score, as compact rows. Each row has an adKey, which get_ad and get_swipe_prompt accept. Valid tag dimensions and slugs are the ones list_taxonomy returns. headline and body are null when the ad's text isn't available (the tags still describe the ad); in rows they are cut at 140 and 280 characters, while get_ad returns them whole. Every other value in a row matches what get_ad returns for that ad. spendEstimate is an estimate based on engagement, not reported spend; spendLowerBound true means the value is a minimum ("at least").
| Name | Type | Req | Description |
|---|---|---|---|
| advertiserId | integer | – | Only ads of this advertiser (the advertiserId shown in search rows) |
| categories | array | – | Advertiser vertical, e.g. health, pet |
| includePastWinners | boolean | – | Also include winners that are no longer running (archive) |
| limit | integer | – | Rows per page, 1-50 |
| media | string | – | Creative type: video, image (image and carousel ads) or all |
| minDays | integer | – | Minimum days running |
| page | integer | – | Page number, starting at 1 (results stop at 1,000 per query) |
| query | string | – | Free text over headline, body, advertiser name and transcript |
| sort | string | – | Order: score (Ad Radar score), reactions, rpd (reactions per day), days (days running) or recent (newest first) |
| tags | object | – | Taxonomy filters: { "<dimension>": ["slug", ...] }. Different dimensions are ANDed, slugs within one are ORed |
| tier | string | – | winner = top 10% by score and running 21+ days; rising = growing. Every ad on the radar has at least $50k estimated spend |
No output schema declared.
No examples provided.
winning_patterns Winning patterns ~99
Returns, for each taxonomy value, how many times more often it appears among winning ads than on average (lift), with adoption (ads, advertisers) and example ads; the same data as the 'What to do now' block of the Ad Radar analytics page. doThis lists the values above average, lower the values below. exampleAdKeys are adKeys that get_ad accepts.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Creative type the lift is computed on |
No output schema declared.
No examples provided.
How do I install the Ad Radar MCP server?
Ad Radar is a hosted endpoint at https://app.ad-radar.dev/api/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 · app.ad-radar.dev
claude mcp add --transport http dev-ad-radar-ad-radar 'https://app.ad-radar.dev/api/mcp'
What is the Ad Radar MCP server?
Ad Radar is an MCP server listed in the public MCP registry as dev.ad-radar/ad-radar. Search winning Meta ads with $50k+ in estimated spend, read hooks and scripts, and draft briefs. This page covers its hosted endpoint (https://app.ad-radar.dev/api/mcp).
Is the Ad Radar MCP server safe to use?
Ad Radar scores 93 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 Ad Radar MCP server expose?
Ad Radar exposes 6 tools: search_ads, get_ad, get_swipe_prompt, list_taxonomy, advertiser_hooks, winning_patterns. Their descriptions and schemas cost roughly 1,059 tokens of context every time the server is loaded.
Does the Ad Radar MCP server require authentication?
Yes. Ad Radar asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Ad Radar MCP server still maintained?
Ad Radar is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Ad Radar MCP server?
VerifyMCP ran 13 checks on Ad Radar, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.