Skip to content

WIA Motion: product video campaigns MCP server

ai.wiamotion/wiamotionwiamotion.aistreamable-httpv1.0.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the WIA Motion: product video campaigns MCP server can do

The WIA Motion: product video campaigns MCP server is published by wiamotion.ai, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: create_campaign and check_campaign), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (create_campaign).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • check_campaignCheck status/progress/artifacts of a wiamotion campaign job by job_id (from create_campaign).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check status/progress/artifacts of a wiamotion campaign job by job_id (from create_campaign).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_campaignCreate a wiamotion product video campaign from 1-4 product photos.Reads text others write1 finding

    Why it is in this group

    • The name "create_campaign" says "create": a word for a change.
    • The input takes a statement or command to run (input.script), which can change anything it can reach.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,123 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...text/bgm are ignored for creator. Returns a job_id — poll it with check_campaign."

      What this check looks for
    Description, as the server wrote it
    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) and direction (gestures/beats). scenes/hook_text/bgm are ignored for creator. Returns a job_id — poll it with check_campaign.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • list_packagesList wiamotion campaign packages — credit cost, video count/duration, resolution.No findings

    Why it is in this group

    • The name "list_packages" says "list": a word for reading.
    Description, as the server wrote it
    List wiamotion campaign packages — credit cost, video count/duration, resolution. Call before create_campaign to pick a package.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:28 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.wiamotion.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://login.smilestory.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.wiamotion.ai/mcp: tools/list returned 3 tools to an anonymous client, including create_campaign (write), check_campaign (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,123 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...text/bgm are ignored for creator. Returns a job_id — poll it with check_campaign."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wiamotion https://mcp.wiamotion.ai/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http wiamotion https://mcp.wiamotion.ai/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__wiamotion__list_packages"
    ],
    "ask": [
      "mcp__wiamotion__create_campaign",
      "mcp__wiamotion__check_campaign"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as wiamotion. Review it before you use it.

Capability tags behind 1 rule
  • mcp__wiamotion__create_campaign untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.wiamotion/wiamotion/verify?hash=b6791784bbde69fdbfa412dddbbf4c4ec540101c16f7dd2ed0e433aeb4995dc8" | jq -e '.changed == false'

Pinned hash b6791784bbde, from Nov 11, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.wiamotion/wiamotion/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.wiamotion/wiamotion
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.wiamotion/wiamotion.svg)](https://radar.anlyon.com/servers/ai.wiamotion/wiamotion)

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

WIA Motion: product video campaigns MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the WIA Motion: product video campaigns MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the WIA Motion: product video campaigns MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the WIA Motion: product video campaigns MCP server have?

3 tools: 2 write, 1 read. create_campaign, check_campaign and list_packages.

Does the WIA Motion: product video campaigns MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the WIA Motion: product video campaigns MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the WIA Motion: product video campaigns MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.