Run1Ads: live Meta ads consultant
REMOTE · RUN1ADS.AI
Live Meta ads consultant for e-commerce. Checks ads, Pixel and store hourly, then gives the one fix.
Available components
Last scanned (5 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 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 Security94
- 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2960 tokens (~155/item across 19 items; 19 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- Tool “get_competitor_changes” rewrote its description, which is the text the model reads security
- Schema quality: 2641 → 2960 ▼ functional
- New tool “get_campaigns” functional
- New tool “get_store_fixes” functional
- 25 Oct 26 +1
- Tool “get_store_checks” rewrote its description, which is the text the model reads security
- Schema quality: 2370 → 2641 ▼ functional
- New tool “get_why_no_buy” functional
- 24 Oct 26 0
- Tool “get_store_checks” rewrote its description, which is the text the model reads security
- Schema quality: 2139 → 2370 ▼ functional
- New tool “get_campaign_funnels” functional
- 22 Oct 26 +1
- Tool “get_today” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://run1ads.ai/mcp/rpc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=run1ads.ai | CN=YE2,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d0775df10bf3c55075c97401ce9c77945c |
| SANs: *.run1ads.ai, run1ads.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of run1ads.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814, 3799 | 8, 8 | Verified |
| run1ads.ai. | 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="run1ads-mcp", resource_metadata="https://run1ads.ai/.well-known/oauth-protected-resource"
Bearer realm="run1ads-mcp", resource_metadata="https://run1ads.ai/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Protected resource metadata
| Document | https://run1ads.ai/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://run1ads.ai/mcp/rpc |
| Authorisation server | https://run1ads.ai |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://run1ads.ai/mcp/rpc | Verified | 200 | |
| http (plaintext) | http://run1ads.ai/mcp/rpc | HTTPS enforced | 301 | https://run1ads.ai/mcp/rpc |
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 →
add_to_fix_list ~168
Add a fix to the brand's Run1Ads fix list. Pass item_key from get_today to add that finding with its steps and the number to track, or pass your own title. Writes to Run1Ads only. Nothing changes in Meta or on your store.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| how | array | – | Steps to apply it. |
| item_key | string | – | The key of a finding from get_today (for example vc_atc or fatigue). |
| pillar | string | – | funnel, journey, fatigue, content, audience, strategy or general. |
| title | string | – | Your own fix title, if not using item_key. |
| why | string | – | – |
No output schema declared.
No examples provided.
ask_consultant ~96
Ask the Run1Ads consultant a question about this brand in plain English. It answers from the saved account data only, with exact steps you can apply. It advises only and never changes anything. Up to 10 questions per brand per day, shared with the app.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| question | string | yes | – |
No output schema declared.
No examples provided.
get_ad_copy_review ~129
Use for "is my ad copy good?" or "why do viewers skip my video?". Returns a review of ads already running: first line, headline, call to action and link, with a score and specific issues, plus video ads from the last 7 days with hook rate, hold rate, where viewers drop off, a visual review of the frames and fix steps. For which ads are tired use get_ad_fatigue. Saved data from the latest review.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_ad_fatigue ~115
Use for "which ads are getting tired?" or "should I refresh my creative?". Returns each ad's frequency, click rate and its change, and hook rate, highest frequency first, so you can see which ads people have seen too often. For the copy and video content itself use get_ad_copy_review; for account totals use get_performance. Saved data, refreshed by the hourly check.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_audiences ~119
Use for "who is buying?", "which placement works best?" or "is my custom audience big enough?". Returns buyers in the period, saved custom audiences with size and whether each is big enough to deliver, and results split by placement (Instagram, Facebook, Reels, Stories). For overall ROAS use get_performance; for funnel drop offs use get_sales_funnel. Saved data from the latest Meta read.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_campaign_funnels ~189
Use for "which campaign sends the best visitors?", "which landing page is weakest?" or "where do visitors from each campaign drop out?". Returns, per campaign (utm_campaign or campaign id, plus visits not tagged with a campaign) for the last 7 and 30 days: visits, the share who left straight away (one page, no scroll past the first quarter), who viewed a product, reached the cart and reached checkout (or "not visible" when the checkout runs on a separate Shopify checkout page), pages per visit, the top landing page, the weakest step, and which campaign is best and weakest. Same table as the app's Funnel by campaign. For Meta's own funnel use get_sales_funnel. Saved data from the daily visitor review.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_campaigns ~169
Use for "how are my campaigns doing?", "which campaign should I fix or give more budget?" or "where does each campaign lose buyers?". Returns each campaign (biggest spend first) with its share of budget, spend and ROAS, then every step from ad click to sale (clicked the ad, looked at a product, added to cart, went to checkout, sales) against similar stores, the one step where it loses the most buyers, what to do, the problem, the fix and what it could be worth in dollars. Same view as Campaigns in the Run1Ads app. Explain ROAS in plain words when the user may not know it.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_competitor_changes ~110
Use for "what are my competitors doing?". Returns recent changes in the brand's chosen competitors' Meta ads as conclusions: what changed, what it means for this brand and what to do (or that nothing is needed). We study their ads so the user does not have to; competitor ads themselves are not shown. Competitors are set in the Run1Ads app.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_fix_list ~120
Use for "what have I committed to?" or "did my fix work?". Returns the fixes the user chose to do, filtered by status (open, done or all, default all), each with its fix_id and, once newer data is saved, whether the tracked number moved after the fix was marked done. Use the fix_id with mark_fix_done. For new findings use get_today.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| status | string | – | – |
No output schema declared.
No examples provided.
get_live_alerts ~153
Use for "is anything broken right now?" or "any alerts?". Returns when the hourly live check last ran, today so far, open alerts with critical first (for example spend with no sales, a rejected ad, a broken Pixel or store) and, unless include_resolved is false, alerts resolved in the last 7 days. Each alert says why it matters and how to fix it. get_today shows only the top items; this shows them all. Saved data, checked every hour.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| include_resolved | boolean | – | Include alerts resolved in the last 7 days. |
No output schema declared.
No examples provided.
get_performance ~133
Use for questions about results and goals: "what's my ROAS?", "how much did I spend?", "am I on track this month?". Returns saved Meta ads totals (spend, revenue, ROAS, purchases, click rate, cost per click, frequency) and this month's ROAS goal with the gap to it. For where buyers drop out use get_sales_funnel; for per ad tiredness use get_ad_fatigue. Saved data, refreshed by the hourly check.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_sales_funnel ~128
Use for "where am I losing buyers?" or "people click but don't buy". Returns each step from ad click to purchase as how many in 1,000 move on, the e-commerce benchmark per 1,000, above or below, the trend, and which step loses the most buyers. For totals like spend and ROAS use get_performance; for why visitors leave the store use get_store_checks. Saved data, refreshed by the hourly check.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_store_checks ~231
Use for questions about the store and tracking, not the ads: "is my Pixel working?", "does my store work in the Instagram browser?", "why do visitors from my ads leave?". Returns whether the store works inside the Instagram and Facebook app browser, whether Add to Cart shows on mobile, whether the Meta Pixel fired, five store scores out of 100, the weakest product pages, and the "Problems to fix" for visitors from Meta ads (landing pages they leave straight away, app layers or buttons that ignore taps, store script errors, weak campaigns, slow pages), each with the numbers, why it matters, fix steps and example visits, plus where they leave. Also the top 3 causes of "Why visitors are not buying" (all of them: get_why_no_buy). For funnel rates use get_sales_funnel; for each campaign's visit to cart funnel use get_campaign_funnels. Saved data from the latest daily store walk and daily visitor review.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_store_fixes ~130
Use for "what should I fix on my website?" or "what on my store is costing me sales?". Returns the problems on the store that cost sales from every campaign, each listed once and ranked by impact, with what we saw, the fix, how long it takes and who does it, and what it could be worth in dollars. Found from visits from the brand's Meta ads, no recordings kept. Same view as Store fixes in the Run1Ads app.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_today ~213
Start here for "what should I do today?" or "what's wrong with my Meta ads?". Returns today's brief: the one fix to do first, other findings ranked by buyers lost (each with its item_key, the number behind it and exact steps), what changed, what is working and the live check status. It summarises the other tools; use get_performance for full numbers, get_live_alerts for every alert, get_sales_funnel for each funnel step. Also returns the Today screen: needs_you_now (critical live alerts, shown first), the headline (for example "3 fixes could lift your ROAS from 1.9x to about 2.6x", all estimates) and up to 3 fixes with problem, fix and worth. Pass an item_key to add_to_fix_list or send_paused_draft. Saved data from the latest hourly check.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
get_why_no_buy ~246
Use for "why are visitors from my Meta ads not adding to cart, not checking out or not buying?". Returns the stage strip from visit to product, add to cart, checkout and purchase (with counts, or "not visible" when we cannot see that step yet), the biggest drop against the e-commerce benchmark, and the likely causes ranked by buyers lost (about), each with its stage, how likely it is (high, medium, low), what we saw with the numbers, the likely cause, 2 to 4 fix steps and what would confirm it. Covers traffic and targeting, ad to page promise, technical problems (in app browser, speed, pop ups, failed adds, sold out products, the Pixel), the product page, cart and checkout friction, measurement gaps and the Meta account. Also lists what we cannot see yet and how to see it (for example the optional Shopify checkout pixel). Same as the app's "Why visitors are not buying". Saved data from the daily visitor review, computed on demand when missing.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
No output schema declared.
No examples provided.
list_brands ~73
List the brands this Run1Ads account can open, with each brand id, name and whether Meta is connected. Use it first when the user manages more than one brand or names a brand, then pass brand_id to the other tools. Every other tool uses the most recently updated brand when brand_id is left out.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_fix_done ~89
Mark a fix on the fix list as done. Run1Ads records the number at that moment so it can show whether the fix worked once newer data is saved. Writes to Run1Ads only.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| fix_id | integer | yes | The fix id from get_fix_list. |
No output schema declared.
No examples provided.
send_paused_draft ~198
Send one finding from get_today to the brand's own Meta ad account as a PAUSED campaign and ad set, so you can finish and switch it on yourself in Ads Manager. Nothing spends. Only findings marked draftable can be sent. Only use this when the user has clearly asked for it, and pass confirm true. Without confirm it returns a preview and sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | – | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| confirm | boolean | – | Must be true, and only after the user explicitly asked to send this draft. |
| daily_budget_usd | number | – | Daily budget saved on the paused draft. It does not spend until you switch the draft on. |
| item_key | string | yes | The key of a draftable finding from get_today (fatigue, creative_copy, placement or lookalike). |
| objective | string | – | – |
No output schema declared.
No examples provided.
How do I install the Run1Ads: live Meta ads consultant MCP server?
Run1Ads: live Meta ads consultant is a hosted endpoint at https://run1ads.ai/mcp/rpc, 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 · run1ads.ai
claude mcp add --transport http ai-run1ads-consultant 'https://run1ads.ai/mcp/rpc'
What is the Run1Ads: live Meta ads consultant MCP server?
Run1Ads: live Meta ads consultant is an MCP server listed in the public MCP registry as ai.run1ads/consultant. Live Meta ads consultant for e-commerce. Checks ads, Pixel and store hourly, then gives the one fix. This page covers its hosted endpoint (https://run1ads.ai/mcp/rpc).
Is the Run1Ads: live Meta ads consultant MCP server safe to use?
Run1Ads: live Meta ads consultant scores 85 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 Run1Ads: live Meta ads consultant MCP server expose?
Run1Ads: live Meta ads consultant exposes 19 tools: list_brands, get_today, get_campaigns, get_store_fixes, get_performance, and 14 more. Their descriptions and schemas cost roughly 2,809 tokens of context every time the server is loaded.
Does the Run1Ads: live Meta ads consultant MCP server require authentication?
Yes. Run1Ads: live Meta ads consultant 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 Run1Ads: live Meta ads consultant MCP server still maintained?
Run1Ads: live Meta ads consultant is still listed as active in the MCP registry. We last reached this channel on 5 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 Run1Ads: live Meta ads consultant MCP server?
VerifyMCP ran 13 checks on Run1Ads: live Meta ads consultant, 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.