# WIA Motion: product video campaigns (remote · mcp.wiamotion.ai)

Create product video campaigns from 1-4 product photos and track them. Requires an API key.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `mcp.wiamotion.ai`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ai-wiamotion-wiamotion/mcp.md), [page](https://verifymcp.io/servers/ai-wiamotion-wiamotion/mcp)

## Channel facts

- Endpoint: `https://mcp.wiamotion.ai/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-10-23.

- **Endpoint Security**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1489 tokens (~372/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 WIA Motion: product video campaigns MCP server?

WIA Motion: product video campaigns is a hosted endpoint at https://mcp.wiamotion.ai/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.

### Claude

```bash
claude mcp add --transport http ai-wiamotion-wiamotion 'https://mcp.wiamotion.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-wiamotion-wiamotion": {
      "url": "https://mcp.wiamotion.ai/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.ai-wiamotion-wiamotion]
url = "https://mcp.wiamotion.ai/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  ai-wiamotion-wiamotion:
    url: "https://mcp.wiamotion.ai/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "ai-wiamotion-wiamotion": {
      "type": "http",
      "url": "https://mcp.wiamotion.ai/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-10-23 (score 72, +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-10-22 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-21 (score 71, +38)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Authorization: fail → partial
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-17 (score 33)

First indexed and scored.

## MCP tools (3)

### `list_packages` (~34 tokens)

List wiamotion campaign packages — credit cost, video count/duration, resolution. Call before create_campaign to pick a package.

### `create_campaign` (~1365 tokens)

Create a wiamotion product video campaign from 1-4 product photos. Produces finished 1080x1920 video(s) + thumbnail(s) + multi-language metadata (never a raw/unfinished clip) and deducts credits from the caller's account. Package tiers: "trial" (1 video, watermarked, 25cr, 3-language metadata), "starter" (1 video, 50cr, 254-language metadata), "launch" (3 videos — hook/how-to/brand mood — 254-language metadata, 125cr), "story" (everything in launch plus one 60-90s cinematic brand short on a premium engine, 400cr). DIRECT YOUR OWN CINEMATOGRAPHY: write distinct scene prompts (English, one short cinematic camera direction each) — this is what makes the result good, the server will not invent creative direction for you. Videos are subtitle-free by default (globally reusable); on-screen text (hook_text / endcard_text) is OPT-IN — omit both unless you specifically want burned-in copy for one language. For "starter"/"trial" use scenes[] (2-4 scenes, one video). For "launch"/"story" use hook_scenes[]/howto_scenes[]/brand_scenes[] (2-4 scenes each, one set per video role) — omit any of these to fall back to a generic template for that video. For "story" additionally use story_scenes[] (8-12 scenes) for the brand short — think in classic beats: hook, development, climax, resolution into the endcard. The server always appends a standard anti-distortion guard to every scene prompt server-side (keeps the product/printed text exactly as in the reference photo, no warping) — do not add your own "no distortion" wording, just describe the shot. Prefer image_urls over images_base64 when the photos are already hosted somewhere — base64 request bodies are capped at 8MB total (~1MB/photo) and get rejected past that. "creator" (200 credits, 2026-09-25) = a realistic on-screen presenter holds the product and speaks YOUR script with lip-sync (~12s, up to 15s): pass persona (who appears), setting (where), language, script (what they say — hook first, then proof), optional gender (voice) a…

Input parameters:

- `accept_text_risk`: Set true ONLY after the user explicitly agrees to proceed despite a source_text_risk rejection (the uploaded image contains heavy printed marketing copy, which AI video generation will garble; garble…
- `bgm_mood` (string): Background music mood, applied to every video in the campaign. Omit for a deterministic per-job default.
- `brand_chain`: "launch"/"story" only. When true, each brand_scenes[] shot after the first is generated from the LAST FRAME of the previous shot instead of the original product photo — use this when your scenes desc…
- `brand_scenes` (array): "launch"/"story" only — 2-4 scenes for the brand-mood video. Omit to fall back to a generic atmospheric-lifestyle template.
- `description` (string): Short product description
- `direction` (string): "creator" only — optional gestures, camera moves and beats.
- `endcard_text` (string): OPTIONAL text on the closing brand card, ≤30 chars. Omit (default) for a clean logo-only endcard with no copy — globally reusable. Provide only to burn in a caption for one specific language.
- `gender` (string): "creator" only — voice gender (default f).
- `hook_scenes` (array): "launch"/"story" only — 2-4 scenes for the hook video. Omit to fall back to a generic hero+detail template.
- `hook_text` (string): OPTIONAL on-screen hook headline, ≤30 chars. Text overlays are opt-in — OMIT for clean, no-caption output that is reusable in any language/market (the default). Provide only when you deliberately wan…
- `howto_scenes` (array): "launch"/"story" only — 2-4 scenes for the how-to/demo video. Omit to fall back to a generic hands-on-demo template.
- `image_urls` (array): 1-4 publicly fetchable URLs — either direct product photo files (jpg/png), or product detail-page URLs (e.g. a Coupang/Amazon listing) with an og:image/twitter:image meta tag, which the server will f…
- `images_base64` (array): 1-4 base64-encoded product photos, alternative to image_urls. Total request body capped at 8MB — use image_urls for larger photos.
- `language` (string): "creator" only — spoken language of the script.
- `package` (string): Package tier — see tool description for what each builds and costs.
- `persona` (string): "creator" only — who appears on screen: age, look, outfit, mood.
- `product_name` (string, required): Product name
- `scenes` (array): "starter"/"trial" only — 2-4 distinct scenes cut together for the single video (no looping/padding). Omit to fall back to a generic 2-scene hero+detail template.
- `script` (string): "creator" only — the spoken line, about 12 seconds (ja/zh ≤90 chars, ko ≤120, en/ar/hi ≤200, others ≤260).
- `setting` (string): "creator" only — where it is filmed: place, light, camera.
- `story_scenes` (array): "story" only — 8-12 scenes for the 60-90s cinematic brand short (hook → development → climax → resolution). Omit to fall back to a generic dome-style 8-scene template.

### `check_campaign` (~43 tokens)

Check status/progress/artifacts of a wiamotion campaign job by job_id (from create_campaign).

Input parameters:

- `job_id` (string, required): job_id returned by create_campaign

## Diagnostics

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

## Score history

- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 33
- 2026-10-19: 33
- 2026-10-18: 33
- 2026-10-17: 33

## Common questions

### What is the WIA Motion: product video campaigns MCP server?

WIA Motion: product video campaigns is an MCP server listed in the public MCP registry as ai.wiamotion/wiamotion. Create product video campaigns from 1-4 product photos and track them. Requires an API key. This page covers its hosted endpoint (https://mcp.wiamotion.ai/mcp).

### Is the WIA Motion: product video campaigns MCP server safe to use?

WIA Motion: product video campaigns scores 72 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 WIA Motion: product video campaigns MCP server expose?

WIA Motion: product video campaigns exposes 3 tools: list_packages, create_campaign, check_campaign. Their descriptions and schemas cost roughly 1,442 tokens of context every time the server is loaded.

### Does the WIA Motion: product video campaigns MCP server require authentication?

No. We connected to WIA Motion: product video campaigns without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the WIA Motion: product video campaigns MCP server still maintained?

WIA Motion: product video campaigns is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.wiamotion.ai/mcp
- Authorisation metadata: https://mcp.wiamotion.ai/.well-known/oauth-protected-resource/mcp
- Website: https://wiamotion.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-wiamotion-wiamotion/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-wiamotion-wiamotion/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-wiamotion-wiamotion/mcp