# 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.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `run1ads.ai`: 85/100 (this document), [markdown](https://verifymcp.io/servers/ai-run1ads-consultant/run1ads.md), [page](https://verifymcp.io/servers/ai-run1ads-consultant/run1ads)

## Channel facts

- Endpoint: `https://run1ads.ai/mcp/rpc`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-run1ads-consultant 'https://run1ads.ai/mcp/rpc'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-run1ads-consultant": {
      "url": "https://run1ads.ai/mcp/rpc"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-run1ads-consultant": {
      "type": "http",
      "url": "https://run1ads.ai/mcp/rpc"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-run1ads-consultant]
url = "https://run1ads.ai/mcp/rpc"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-run1ads-consultant": {
      "type": "remote",
      "url": "https://run1ads.ai/mcp/rpc",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-run1ads-consultant --url 'https://run1ads.ai/mcp/rpc' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-run1ads-consultant:
    url: "https://run1ads.ai/mcp/rpc"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-run1ads-consultant": {
      "Transport": "http",
      "Url": "https://run1ads.ai/mcp/rpc"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-run1ads-consultant -t streamable-http -u 'https://run1ads.ai/mcp/rpc'
```

### Other

```json
{
  "mcpServers": {
    "ai-run1ads-consultant": {
      "type": "http",
      "url": "https://run1ads.ai/mcp/rpc"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, +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.

### 2026-11-02 (score 84, +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.

### 2026-10-31 (score 83, +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.

### 2026-10-29 (score 82, +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.

### 2026-10-26 (score 81, +1)

- [security] Tool “get_competitor_changes” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2641 → 2960
- [functional] New tool “get_campaigns”
- [functional] New tool “get_store_fixes”

### 2026-10-25 (score 80, +1)

- [security] Tool “get_store_checks” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2370 → 2641
- [functional] New tool “get_why_no_buy”

### 2026-10-24 (score 79, 0)

- [security] Tool “get_store_checks” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2139 → 2370
- [functional] New tool “get_campaign_funnels”

### 2026-10-22 (score 79, +1)

- [security] Tool “get_today” rewrote its description, which is the text the model reads

## MCP tools (19)

### `list_brands` (~73 tokens)

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.

### `get_today` (~213 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_campaigns` (~169 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_store_fixes` (~130 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_performance` (~133 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_sales_funnel` (~128 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_live_alerts` (~153 tokens)

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.

Input parameters:

- `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.

### `get_store_checks` (~231 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_campaign_funnels` (~189 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_why_no_buy` (~246 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_ad_fatigue` (~115 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_ad_copy_review` (~129 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_audiences` (~119 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_competitor_changes` (~110 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.

### `get_fix_list` (~120 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.
- `status` (string)

### `add_to_fix_list` (~168 tokens)

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.

Input parameters:

- `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)

### `mark_fix_done` (~89 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.
- `fix_id` (integer, required): The fix id from get_fix_list.

### `ask_consultant` (~96 tokens)

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.

Input parameters:

- `brand_id` (string): Brand id from list_brands. Leave it out to use your most recently updated brand.
- `question` (string, required)

### `send_paused_draft` (~198 tokens)

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.

Input parameters:

- `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, required): The key of a draftable finding from get_today (fatigue, creative_copy, placement or lookalike).
- `objective` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-run1ads-consultant/run1ads#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 78
- 2026-10-20: 79

## Common questions

### 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.

## Links

- Remote endpoint: https://run1ads.ai/mcp/rpc
- Website: https://run1ads.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-run1ads-consultant/run1ads.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-run1ads-consultant/run1ads/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-run1ads-consultant/run1ads.json
- HTML version of this page: https://verifymcp.io/servers/ai-run1ads-consultant/run1ads