PPC Ad Editor
REMOTE · STUDIO.PPCADEDITOR.COM
Preview Google Search, PMax, Display, YouTube, Meta and LinkedIn ad mockups in chat. No sign-in.
Available components
Last scanned (16 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 6 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 Security80
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1309 tokens (~436/item across 3 items; 2 tools + 1 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 94% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 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
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Resource “ad-preview” now points somewhere else: ui://pcade/ad-preview-bc26e4f36168.html → ui://pcade/ad-preview-3f803c4c3981.html security
- Tool “preview_ad” rewrote its description, which is the text the model reads security
- Schema quality: 373 → 436 ▼ functional
- “preview_ad” reworded the description of “descriptions” cosmetic
- “preview_ad” reworded the description of “extensions” cosmetic
- “preview_ad” reworded the description of “primary_texts” cosmetic
- 4 Nov 26 +1
- Resource “ad-preview” now points somewhere else: ui://pcade/ad-preview-b94fc07f5028.html → ui://pcade/ad-preview-bc26e4f36168.html security
- 3 Nov 26 +1
- Resource “ad-preview” now points somewhere else: ui://pcade/ad-preview-bd4f00799481.html → ui://pcade/ad-preview-b94fc07f5028.html security
- Tool “preview_ad” rewrote its description, which is the text the model reads security
- Schema quality: 296 → 373 ▼ functional
- Tool coverage: 44% → 94% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- “preview_ad” reworded the description of “business_name” cosmetic
- “preview_ad” reworded the description of “call_to_action” cosmetic
- “preview_ad” reworded the description of “descriptions” cosmetic
- “preview_ad” reworded the description of “display_path_1” cosmetic
- “preview_ad” reworded the description of “display_path_2” cosmetic
- “preview_ad” reworded the description of “headlines” cosmetic
- “preview_ad” reworded the description of “long_headlines” cosmetic
- “preview_ad” reworded the description of “primary_texts” cosmetic
- 2 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 6 Nov 2026 · Probed https://studio.ppcadeditor.com/api/mcp/preview
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=studio.ppcadeditor.com | CN=YR1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | RSA 2048 | SHA256-RSA | 5f15fa022cc66da2afaaa2668b98802fb58 |
| SANs: studio.ppcadeditor.com | ||||||
| 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 studio.ppcadeditor.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| ppcadeditor.com. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://studio.ppcadeditor.com/api/mcp/preview | Verified | 200 | |
| http (plaintext) | http://studio.ppcadeditor.com/api/mcp/preview | HTTPS enforced | 308 | https://studio.ppcadeditor.com/api/mcp/preview |
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 →
get_ad_formats Get ad format specs ~43
Returns the full specification for each ad format: field counts, character limits and supported media.
| Name | Type | Req | Description |
|---|---|---|---|
| formats | array | – | Optional filter: only return specs for these formats |
No output schema declared.
No examples provided.
preview_ad Preview an ad ~1,215
Show a realistic mockup of one ad (Google Search, Display, Performance Max, Demand Gen, YouTube, Facebook/Instagram, LinkedIn, Microsoft Advertising/Bing, OpenAI chat ads, X, Reddit) right in the chat. No account needed. The ad copy comes from the caller. Images are hosted HTTPS URLs in images[] / logos[], for example from the advertiser's website; this tool never generates images, and Google Search ads need none. Studio, YouTube and www.ppcadeditor.com images load directly. Any other HTTPS image is shown through a signed URL on studio.ppcadeditor.com. One format per call. The result includes save_url, a link where the user can save the ad to a free PPC Ad Editor account, edit it, and get a share link for a client. Format specs (items allowed per field, max characters per item): - RSA (Google Search): headlines 3-15 (max 30 chars), descriptions 2-4 (max 90 chars) - RDA (Google Display): headlines 1-5 (max 30 chars), long_headlines 0-1 (max 90 chars), descriptions 1-5 (max 90 chars) - PMAX (Performance Max): headlines 1-15 (max 30 chars), long_headlines 0-5 (max 90 chars), descriptions 1-5 (max 90 chars) - DEMAND_GEN (Google Demand Gen): headlines 1-5 (max 40 chars), long_headlines 0-5 (max 90 chars), descriptions 1-5 (max 90 chars) - META_SINGLE (Facebook/Instagram single): headlines 1-5 (max 40 chars), descriptions 0-5 (max 25 chars), primary_texts 0-5 (max 125 chars) - META_CAROUSEL (Facebook/Instagram carousel): headlines 1-10 (max 40 chars), descriptions 0-10 (max 25 chars), primary_texts 0-5 (max 125 chars) - META_STORY (Facebook/Instagram story): primary_texts 0-5 (max 125 chars) - LINKEDIN_SINGLE (LinkedIn single): headlines 1 (max 200 chars), descriptions 1 (max 300 chars), primary_texts 0-1 (max 600 chars) - LINKEDIN_CAROUSEL (LinkedIn carousel): headlines 1-10 (max 45 chars), descriptions 1-10 (max 70 chars), primary_texts 0-1 (max 600 chars) - YOUTUBE (YouTube): headlines 1-5 (max 30 chars), long_headlines 0-1 (max 90 chars), descriptions 1-5 (max 90 ch…
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | – | Business name shown on the ad. 25 characters. |
| call_to_action | string | – | Button label, for example Learn more. 30 characters. |
| descriptions | array | – | Not the Facebook or Instagram body. On META_SINGLE and META_CAROUSEL this is the optional link line under the headline, 25 characters, and it may be omitted. Body copy belongs in primary_texts (125 c… |
| display_path_1 | string | – | Optional Google display path. 15 characters. |
| display_path_2 | string | – | Optional second Google display path. 15 characters. |
| extensions | object | – | Ad extensions (aka ad assets). Search formats only (RSA, PMAX, MICROSOFT_RSA) — ignored on Meta/LinkedIn/YouTube/CHATGPT_AD/X/Reddit. |
| final_url | string | yes | – |
| format | string | yes | Ad format of the mockup. Field limits per format are listed in the format specs. |
| headlines | array | – | Short headlines. The character limit depends on the format and is listed in this tool's format specs. Google Search headlines are 30 characters. There is no single limit for every format. |
| images | array | – | Core ad-body images (Meta hero, Carousel cards, PMAX assets, etc.). Feature-gated per format. Google image EXTENSIONS (shown below an RSA text ad) go in extensions.images. |
| logos | array | – | Core ad-body logos (brand/profile image shown next to the ad on Meta, LinkedIn, RDA, PMAX). |
| long_headlines | array | – | Long headlines for Performance Max, Display and Demand Gen. Character limits are in the format specs. Google Search and Meta do not use this field. |
| name | string | – | Optional name for the ad, used if the user saves it |
| primary_texts | array | – | Body copy for Facebook, Instagram and LinkedIn. META_SINGLE, META_CAROUSEL and META_STORY: 125 characters. X_AD: the post (primary_texts[0], required). REDDIT_AD: the post headline (primary_texts[0],… |
| videos | array | – | Core ad-body videos (YouTube URLs). Primary for YOUTUBE format, optional for Meta/PMAX/RDA. |
No output schema declared.
No examples provided.
How do I install the PPC Ad Editor MCP server?
PPC Ad Editor is a hosted endpoint at https://studio.ppcadeditor.com/api/mcp/preview, 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 · studio.ppcadeditor.com
claude mcp add --transport http com-ppcadeditor-ppc-ad-editor 'https://studio.ppcadeditor.com/api/mcp/preview'
What is the PPC Ad Editor MCP server?
PPC Ad Editor is an MCP server listed in the public MCP registry as com.ppcadeditor/ppc-ad-editor. Preview Google Search, PMax, Display, YouTube, Meta and LinkedIn ad mockups in chat. No sign-in. This page covers its hosted endpoint (https://studio.ppcadeditor.com/api/mcp/preview).
Is the PPC Ad Editor MCP server safe to use?
PPC Ad Editor scores 74 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 PPC Ad Editor MCP server expose?
PPC Ad Editor exposes 2 tools: preview_ad, get_ad_formats. Their descriptions and schemas cost roughly 1,258 tokens of context every time the server is loaded.
Does the PPC Ad Editor MCP server require authentication?
No. We connected to PPC Ad Editor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PPC Ad Editor MCP server still maintained?
PPC Ad Editor is still listed as active in the MCP registry. We last reached this channel on 6 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 PPC Ad Editor MCP server?
VerifyMCP ran 14 checks on PPC Ad Editor, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.