# Recao (remote · recao.app)

Rank a competitor's EU App Store ads by longevity. From Apple's official Ad Repository.

- Trust score: 73/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `recao.app`: 73/100 (this document), [markdown](https://verifymcp.io/servers/app-recao-recao-mcp/api-mcp.md), [page](https://verifymcp.io/servers/app-recao-recao-mcp/api-mcp)

## Channel facts

- Endpoint: `https://recao.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2444 tokens (~143/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http app-recao-recao-mcp https://recao.app/api/mcp
```

### Codex

```toml
[mcp_servers.app-recao-recao-mcp]
url = "https://recao.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-recao-recao-mcp": {
      "type": "remote",
      "url": "https://recao.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-recao-recao-mcp --url https://recao.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-recao-recao-mcp:
    url: "https://recao.app/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "app-recao-recao-mcp": {
      "type": "http",
      "url": "https://recao.app/api/mcp"
    }
  }
}
```

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-08-03 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 71, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 66, +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.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (17)

### `search_app_advertiser` (~68 tokens)

Search the Apple Ad Repository for apps or developers advertising on the EU App Store. Returns ids to use with get_competitor_ads. Start here with your competitor's app name.

Input parameters:

- `name` (string, required): App or developer name to search for
- `types` (string)

### `get_competitor_ads` (~182 tokens)

Get all Apple App Store ads a competitor has run (EU storefronts, up to 1 year back), with creative copy, placements, formats, and an inferred winner analysis: ads sorted by how long they've been running (longevity = the advertiser keeps paying = likely converting). Source: official Apple Ad Repository (DSA transparency data).

Input parameters:

- `countries` (array): EU country codes to filter (default: all 25). Available: AT,BE,BG,HR,CY,CZ,DK,EE,FI,FR,DE,GR,HU,IE,IT,LV,LU,NL,PL,PT,RO,SK,SI,ES,SE
- `datePreset` (string)
- `id` (number, required): appId or developerId from search_app_advertiser
- `type` (string)

### `get_ad_details` (~73 tokens)

Get full details and locale/creative variations for one specific ad (use adId from get_competitor_ads). Shows every language variant, creative asset URLs, and icon variations. Useful to see how a competitor localizes a winning ad.

Input parameters:

- `adId` (string, required)
- `datePreset` (string)

### `get_playbook` (~83 tokens)

Get a Recao GTM playbook: the go-to-market moves a solo app founder's agent runs, wired to the competitor data tools. Start with 'the-roadmap' (diagnoses the founder's stage and its binding constraint, then routes you to the right playbook). Call with no slug to list all playbooks.

Input parameters:

- `slug` (string)

### `sign_up` (~182 tokens)

Request a free Recao account for your human. This does NOT create an active account: it registers a PENDING one and emails your human an activation link; nothing works and no terms are accepted until they click it (the human accepts the terms at activation, not you). The API key in the response stays inert until then. Consent stays with the human, so calling this is a request, not a decision made for them: in an interactive session their approval of this tool call is the go-ahead; if you run autonomously, surface this step to your human instead of calling it. After activation, reconnect with header `Authorization: Bearer <key>`.

Input parameters:

- `app_name` (string): The user's own app (App Store name), so reports and memory attach to it
- `email` (string, required): The account owner's email (the human founder's)

### `upgrade` (~71 tokens)

Get the checkout link to upgrade this account to a paid plan (Indie €29/mo: 10 competitors + weekly auto-reports; Pro €79/mo: 25 competitors, new channels first, full API). Payment happens in the browser. Hand the link to the human.

Input parameters:

- `plan` (string, required)

### `memory_index` (~64 tokens)

List this account's company memory, one line per entry (name + description), newest first. Traverse index-first: scan this, then memory_recall(name) for full bodies. Memory accrues automatically from your competitor scans (exhaust) and from your own memory_note writes.

### `memory_recall` (~42 tokens)

Read one memory entry's full body by name (get names from memory_index).

Input parameters:

- `name` (string, required): Memory name (kebab-case slug from memory_index)

### `memory_note` (~111 tokens)

Write (or update) a memory entry on this account: decisions, campaign outcomes, learnings. Use a short kebab-case name and a one-line description (that's the index line); details go in body. Your future sessions and Recao's weekly reports read this.

Input parameters:

- `body` (string, required): Full content (markdown fine)
- `description` (string, required): One-line summary for the index
- `name` (string, required): Short kebab-case slug, e.g. 'campaign-tiktok-hooks-june'

### `roadmap_status` (~89 tokens)

Where the founder's agent starts its go-to-market work: diagnose which stage of the Recao Roadmap this account is in (S0 pre-launch to S4 scale), the binding constraint, and the playbook to run. Reads your scans and memory. Sharpen it: write a memory_note named 'company-stage' with your MRR band and funnel numbers, and this tool will use it.

### `generate_avatar` (~196 tokens)

Generate a UGC persona: your agent passes a persona brief (physical look plus vibe of one invented creator), and we return stills of that invented person plus an avatar_id. The persona brief anchors the same character in generate_clips takes, and the stills are the customer's reference artifact for the creative. Ask for up to 3; the default model returns a single strong base still, imagen and flux return the full set. Metered per generation; the price is shown in the response. Paid plans only.

Input parameters:

- `count` (integer): How many stills to request (2 to 3). The default model returns 1 regardless; imagen and flux honor this.
- `model` (string): Image model. Default seedream-4.0 (lowest cost).
- `persona_brief` (string, required): Physical description plus vibe of the invented UGC creator. One person (age, look, styling, setting, energy).

### `generate_clips` (~554 tokens)

Render UGC video scenes as ad-ready clips, metered per second of video (the estimate shows the exact price before anything renders). Pass 3 to 6 scenes (5 to 8 seconds each, one action per scene, spoken lines at most 20 words; empty spoken_line for silent characters). Consecutive scenes pack into single TAKES of up to 15 seconds, one generation each. HOW CHARACTER IDENTITY WORKS, read carefully: all characters are described in TEXT (avatar_id resolves to its persona brief; or write the persona field yourself, covering one character or a whole ensemble). The video model rejects every image that contains a person, so no photo can anchor a face. Text keeps a character IDENTICAL only WITHIN a take; ACROSS takes it preserves the look and styling but the exact face can drift, and neither avatar_id nor persona prevents that. Structure your script so scenes where the same character must be recognizably identical sit adjacent and fit one take (15s or less); treat cross-take appearances as different shots of a matching character, and review the result. reference_image_urls (up to 9 https images) keeps real products or props on-model in every take; these images must contain no people. Without confirm, it validates the contract and returns the per-scene price estimate in EUR, and makes nothing. With confirm=true it starts the metered render and returns a job_id: rendering runs in the background over a few minutes, so poll clips_status with that id to get per-scene clip URLs plus the uncut takes. Paid plans only.

Input parameters:

- `aspect` (string): Output aspect ratio
- `avatar_id` (string): Avatar id from generate_avatar (starts with av_). Its persona brief describes the recurring character in text; identity holds within a take only, not across takes.
- `confirm` (boolean): Set true to start the metered render. Returns a job_id to poll with clips_status.
- `model` (string): seedance-2.0 (default, highest quality) or seedance-2.0-fast (same generation, faster and cheaper).
- `persona` (string): Alternative to avatar_id: describe the recurring character or the full ensemble (several characters) in words. Same limits: identity holds within a take, not across takes. Ignored when avatar_id is p…
- `reference_image_urls` (array): Up to 9 https image URLs of products or props to keep on-model in every take. No people in these images.
- `scenes` (array, required): 3 to 6 scenes in order. Adjacent scenes sharing a character land in the same take when their combined length allows it.

### `clips_status` (~88 tokens)

Check a generate_clips render job by its job_id. Returns the status (processing, done, or error). When done, returns the finished clip URLs, the model used, and the booked cost in EUR. When it errored, returns the reason. Only jobs on your own account are visible.

Input parameters:

- `job_id` (string, required): The job_id returned by generate_clips with confirm=true

### `assemble_video` (~356 tokens)

Stitch rendered scene clips into one ad-ready MP4 with burned-in subtitles and crossfades. Pass 1 to 6 clips in order, each with its mp4 url, its duration in seconds (3 to 12), and an optional subtitle line to burn over that clip. Every clip is scaled and padded to the chosen aspect (9:16 default 1080x1920, 1:1 1080x1080, or 16:9 1920x1080). Optional intro and outro title cards: pass intro/outro as { text, duration_s? } to bookend the ad with a centred title card (1 to 5 seconds, default 2) that crossfades into the video; cards do not count toward the 6-clip limit. Assembly is our compute, so it carries a small flat fee (about 0.12 EUR), booked only when the file is produced, against your trust cap. Runs in the background over up to a couple of minutes and returns a job_id: poll assemble_status with it to get the finished MP4 url. Feed it the clips from clips_status (map each to url, duration_s, subtitle). Paid plans only.

Input parameters:

- `aspect` (string): Output aspect ratio: 9:16 (default, 1080x1920), 1:1 (1080x1080), or 16:9 (1920x1080).
- `clips` (array, required): 1 to 6 clips in playback order
- `intro` (object): Optional intro title card shown before the clips.
- `outro` (object): Optional outro title card shown after the clips (e.g. a call to action).

### `assemble_status` (~88 tokens)

Check an assemble_video job by its job_id. Returns the status (processing, done, or error). When done, returns the final MP4 url, the aspect, clip count, total duration, and the booked cost in EUR. When it errored, returns the reason. Only jobs on your own account are visible.

Input parameters:

- `job_id` (string, required): The job_id returned by assemble_video

### `usage` (~51 tokens)

Show this account's metered generation spend this period and its billing position: the usage cap, what has accrued toward it, and whether generation is waiting on a payment. Use it to report costs back to your human.

### `whoami` (~25 tokens)

Show the authenticated account (plan, email, verification state), or confirm you're anonymous.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-recao-recao-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 73
- 2026-08-02: 72
- 2026-08-01: 72
- 2026-07-31: 71
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://recao.app/api/mcp
- Repository: https://github.com/fernando-menendez/recao-mcp
- Website: https://recao.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-recao-recao-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-recao-recao-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/app-recao-recao-mcp/api-mcp