# Motion by Frapea (remote · motion.frapea.com)

One sentence to a finished animation: your AI writes motion graphics as code and checks real frames.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

> **Recent critical change**: Authorization (2026-10-22). See the changelog below before you install this server.

## Components

- remote · `motion.frapea.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-frapea-motion/motion.md), [page](https://verifymcp.io/servers/com-frapea-motion/motion)

## Channel facts

- Endpoint: `https://motion.frapea.com/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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (close_composition).
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2415 tokens (~120/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Motion by Frapea MCP server?

Motion by Frapea is a hosted endpoint at https://motion.frapea.com/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 com-frapea-motion 'https://motion.frapea.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-frapea-motion": {
      "url": "https://motion.frapea.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-frapea-motion": {
      "type": "http",
      "url": "https://motion.frapea.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-frapea-motion]
url = "https://motion.frapea.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-frapea-motion --url 'https://motion.frapea.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-frapea-motion:
    url: "https://motion.frapea.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-frapea-motion": {
      "Transport": "http",
      "Url": "https://motion.frapea.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-frapea-motion -t streamable-http -u 'https://motion.frapea.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-frapea-motion": {
      "type": "http",
      "url": "https://motion.frapea.com/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 68, +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-22 (score 67, +1)

- [critical regression] Authorization: unverified → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “delete_media”, which the server declares destructive
- [security] Tool “check_playback” rewrote its description, which is the text the model reads
- [security] Tool “close_composition” rewrote its description, which is the text the model reads
- [security] Tool “connect” rewrote its description, which is the text the model reads
- [security] Tool “create_composition” rewrote its description, which is the text the model reads
- [security] Tool “create_session” rewrote its description, which is the text the model reads
- [security] Tool “get_composition” rewrote its description, which is the text the model reads
- [security] Tool “get_media” rewrote its description, which is the text the model reads
- [security] Tool “get_problems” rewrote its description, which is the text the model reads
- [security] Tool “inspect_composition” rewrote its description, which is the text the model reads
- [security] Tool “inspect_media” rewrote its description, which is the text the model reads
- [security] Tool “list_compositions” rewrote its description, which is the text the model reads
- [security] Tool “list_media” rewrote its description, which is the text the model reads
- [security] Tool “organize_media” rewrote its description, which is the text the model reads
- [security] Tool “put_media” rewrote its description, which is the text the model reads
- [security] Tool “read_skill” rewrote its description, which is the text the model reads
- [security] Tool “set_props” rewrote its description, which is the text the model reads
- [security] Tool “tell_user” rewrote its description, which is the text the model reads
- [security] Tool “update_composition” rewrote its description, which is the text the model reads
- [security] Tool “wait_for_tab” rewrote its description, which is the text the model reads
- [security] Tool “close_composition” is now declared destructive
- [security] Tool “set_props” is now declared destructive
- [security] Tool “update_composition” is now declared destructive
- [functional improvement] Schema quality: 149 → 120
- [functional] Destructive annotations: pass → 100
- [cosmetic] Tool “check_playback” changed its title: Check playback
- [cosmetic] Tool “close_composition” changed its title: Close composition
- [cosmetic] Tool “connect” changed its title: Connect to a Motion tab
- [cosmetic] Tool “create_composition” changed its title: Create composition
- [cosmetic] Tool “create_session” changed its title: Start a session without a tab
- [cosmetic] Tool “get_composition” changed its title: Get composition
- [cosmetic] Tool “get_media” changed its title: Get media bytes
- [cosmetic] Tool “get_problems” changed its title: Get problems
- [cosmetic] Tool “inspect_composition” changed its title: Render frames
- [cosmetic] Tool “inspect_media” changed its title: Inspect media
- [cosmetic] Tool “list_compositions” changed its title: List compositions
- [cosmetic] Tool “list_media” changed its title: List media
- [cosmetic] Tool “organize_media” changed its title: Organize media folders
- [cosmetic] Tool “put_media” changed its title: Add media from a URL
- [cosmetic] Tool “read_skill” changed its title: Read a Motion guide
- [cosmetic] Tool “set_props” changed its title: Set composition props
- [cosmetic] Tool “tell_user” changed its title: Show a status line
- [cosmetic] Tool “update_composition” changed its title: Update composition
- [cosmetic] Tool “wait_for_tab” changed its title: Wait for the Motion tab

### 2026-10-20 (score 66, +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-10-18 (score 65, +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-10-16 (score 64, +1)

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

### 2026-10-14 (score 63, +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-13 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 62)

First indexed and scored.

## MCP tools (20)

### `close_composition` (~75 tokens)

Close composition

Closes a composition and removes it from the user's tabs; its source is not kept. Meant for drafts made along the way. Needs an explicit id and never falls back to the active composition.

Input parameters:

- `id` (string, required): The composition to close. Required.
- `token` (string, required): The session token that connect returned.

### `connect` (~80 tokens)

Connect to a Motion tab

Pairs this agent with a Motion browser tab using the eight-character code the user sees under the Connect MCP button (for example K7M4-P2Q9). Returns a session token that every other tool takes. The code works once; the token is what stays valid.

Input parameters:

- `code` (string, required): The eight-character pairing code shown on the Motion page.

### `create_session` (~71 tokens)

Start a session without a tab

Starts a Motion session when the user has no pairing code. Compositions can be created and edited at once; the returned link opens the session in a browser. Rendering frames, playback and anything touching media need that tab open (see wait_for_tab). The scene is kept for 24 hours after the last change.

### `wait_for_tab` (~60 tokens)

Wait for the Motion tab

Waits until the user's Motion tab connects to the session, for example after they open the link from create_session. Returns as soon as it connects, or after about 25 seconds with tabConnected false. Tools that render or touch media need the tab.

### `tell_user` (~199 tokens)

Show a status line

Shows one short status sentence in the user's Motion tab while work is in progress, so they can tell progress from a stall. kind 'done' marks the job finished and 'problem' marks a blocker; step and of draw a progress bar. Changes nothing else. How it fits the workflow: read_skill {topic:'motion-workflow'}.

Input parameters:

- `kind` (string): Omit while working. 'done' ends the job, 'problem' flags a blocker.
- `of` (number): How many there are in total, e.g. 5 — draws a progress bar. Send both or neither, and only when you genuinely know the total; a bar that goes backwards is worse than none.
- `step` (number): Which one you are on, e.g. 2.
- `text` (string, required): One friendly sentence, first person. Not a log line.
- `token` (string, required): The session token that connect returned.

### `read_skill` (~126 tokens)

Read a Motion guide

Returns one of Motion's authoring guides as text. 'motion' is the API contract: what compiles, resolves and renders — compositions written without it usually fail. 'motion-craft' covers timing and design so results do not look generated; 'motion-text' typography; 'motion-effects' named looks; 'motion-transitions' sequencing scenes; 'motion-examples' two contrasting complete pieces; 'motion-workflow' working while the user watches and checking frames; 'motion-review' a structured critique for pieces with an audience and a purpose.

Input parameters:

- `topic` (string, required)

### `list_media` (~101 tokens)

List media

Lists the user's media library: folders, and files with id, name, kind, size and folder. `storage` says whether a file is 'linked' (still on their disk) or 'copied' (held by the browser); a linked file can need the user to re-grant access after a reload.

Input parameters:

- `path` (string): Folder to list. Omit for all.
- `token` (string, required): The session token that connect returned.

### `put_media` (~182 tokens)

Add media from a URL

Adds a file to the library as a new item; nothing existing is replaced. With `url`, the user's browser fetches it, so only public https hosts that send CORS headers work. `data` takes base64 bytes and is limited to about 700 KB, for small generated assets. Larger files on the caller's disk can be sent as an HTTP POST of the raw bytes to /media/upload?token=TOKEN&name=NAME on this server's origin (up to 10 MB).

Input parameters:

- `data` (string): Base64 bytes, for small assets.
- `folder` (string): Folder to put it in. Omit for the root.
- `name` (string, required): Filename, including extension.
- `token` (string, required): The session token that connect returned.
- `url` (string): http(s) URL for the browser to fetch.

### `get_media` (~65 tokens)

Get media bytes

Returns the raw bytes of one file, base64, capped at about 600 KB. For larger files and for video, inspect_media describes the content at a fraction of the size.

Input parameters:

- `id` (string, required)
- `token` (string, required): The session token that connect returned.

### `inspect_media` (~87 tokens)

Inspect media

Looks inside an image or video and returns one contact sheet: each requested moment as a labelled cell in a single image. atSec takes up to 12 timestamps in seconds; omitted, the moments are spread evenly over the clip.

Input parameters:

- `atSec` (array): Up to 12 timestamps.
- `id` (string, required)
- `token` (string, required): The session token that connect returned.

### `organize_media` (~117 tokens)

Organize media folders

Moves files and manages folders. action: 'move' (ids + toFolder), 'createFolder' (name + optional parent), 'deleteFolder' (folder; the files inside move up one level, nothing is deleted). Deleting files is delete_media.

Input parameters:

- `action` (string, required)
- `folder` (string)
- `ids` (array)
- `name` (string)
- `parent` (string)
- `toFolder` (string)
- `token` (string, required): The session token that connect returned.

### `delete_media` (~78 tokens)

Delete media

Deletes files from the user's media library by id. A copied file is gone from the browser; a linked file stays on the user's disk and only leaves the library. Compositions that use a deleted file report it as missing footage.

Input parameters:

- `ids` (array, required): The files to delete.
- `token` (string, required): The session token that connect returned.

### `list_compositions` (~37 tokens)

List compositions

Lists the compositions open in the session, and which one is on screen.

Input parameters:

- `token` (string, required): The session token that connect returned.

### `get_composition` (~62 tokens)

Get composition

Returns one composition in full: manifest, every source file, and current prop values — the state an update_composition edit applies to.

Input parameters:

- `id` (string): Omit for the active one.
- `token` (string, required): The session token that connect returned.

### `create_composition` (~180 tokens)

Create composition

Creates a new composition from TSX source and opens it as a tab in the user's Motion page. `files` maps path to source and must include the entry (default composition.tsx). The API is specific to Motion and documented in read_skill {topic:'motion'}; design guidance is in {topic:'motion-craft'}. A partsBoard prop (default false) can lay out UI-like parts for checking before scenes are built.

Input parameters:

- `durationInFrames` (number, required)
- `entry` (string): Defaults to composition.tsx.
- `files` (object, required)
- `fps` (number, required)
- `height` (number, required)
- `name` (string, required)
- `schema` (object): Props schema; drives the editable controls.
- `token` (string, required): The session token that connect returned.
- `width` (number, required)

### `update_composition` (~121 tokens)

Update composition

Edits an existing composition. Each file sent replaces the file at that path; files not sent are kept. Changing the schema keeps prop values that still have a matching field.

Input parameters:

- `durationInFrames` (number)
- `files` (object)
- `fps` (number)
- `height` (number)
- `id` (string): Omit for the active one.
- `name` (string)
- `schema` (object)
- `token` (string, required): The session token that connect returned.
- `width` (number)

### `set_props` (~62 tokens)

Set composition props

Sets prop values on a composition, the same values the user's controls change. Merged by key; keys sent replace their current values.

Input parameters:

- `id` (string)
- `props` (object, required)
- `token` (string, required): The session token that connect returned.

### `inspect_composition` (~201 tokens)

Render frames

Renders frames of a composition in the user's tab and returns them as one labelled contact sheet; nothing is saved or changed. atFrames takes up to 12 frames; omitted, the sheet is an even spread plus the joins between scenes (labelled "end of a scene", "start of a scene", "mid transition"). One frame comes back at 1560 px, two at 960, for checking detail. `props` are merged over the composition's for this render only, e.g. {partsBoard:true}. Each frame reports its content share (how much is not background); one far below its neighbours is usually a gap between scenes.

Input parameters:

- `atFrames` (array)
- `id` (string): Omit for the active one.
- `props` (object): Merged over the composition's props for this render only, e.g. {partsBoard:true}.
- `token` (string, required): The session token that connect returned.

### `check_playback` (~189 tokens)

Check playback

Plays a composition on the user's stage from the first frame to the last, through the same preview a person watches (which inspect_composition does not use), and reports whether it got to the end. Buffering is allowed; any error ends the run. Answers within about 20 s: {status:"running", at, total} means call again with the same id to keep waiting on the same run. Then {status:"done", verdict:"ok"|"problems", problems, warnings} or {status:"incomplete", reason} (tab hidden, interrupted, edited). It takes over the stage while it runs: the composition under test becomes the one on screen and the preview plays from frame 0. The composition's source and props are not changed.

Input parameters:

- `id` (string): Omit for the active one.
- `token` (string, required): The session token that connect returned.

### `get_problems` (~181 tokens)

Get problems

Lists what went wrong in the user's tab: frames that failed to render (with the frame and the engine's message), a preview that stopped moving and why, compositions that would not load, clips that will not decode, missing footage, failed exports, a page the browser killed — plus warnings. Works while the tab is hidden or closed. `current` belongs to the composition as it is now; `earlier` counts problems an edit has since left behind. Other tool results may also carry a `problems` list of what is new. An empty list covers only what the tab has played; check_playback does a full pass.

Input parameters:

- `id` (string): Only this composition. Omit for all of them.
- `includeWarnings` (boolean): Include warnings (default true).
- `token` (string, required): The session token that connect returned.

## Diagnostics

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

## Score history

- 2026-10-23: 68
- 2026-10-22: 67
- 2026-10-21: 66
- 2026-10-20: 66
- 2026-10-19: 65
- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 62
- 2026-10-12: 62

## Common questions

### What is the Motion by Frapea MCP server?

Motion by Frapea is an MCP server listed in the public MCP registry as com.frapea/motion. One sentence to a finished animation: your AI writes motion graphics as code and checks real frames. This page covers its hosted endpoint (https://motion.frapea.com/mcp).

### Is the Motion by Frapea MCP server safe to use?

Motion by Frapea scores 68 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 Motion by Frapea MCP server expose?

Motion by Frapea exposes 20 tools: close_composition, connect, create_session, wait_for_tab, tell_user, and 15 more. Their descriptions and schemas cost roughly 2,274 tokens of context every time the server is loaded.

### Does the Motion by Frapea MCP server require authentication?

No. We connected to Motion by Frapea without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Motion by Frapea MCP server still maintained?

Motion by Frapea 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://motion.frapea.com/mcp
- Website: https://motion.frapea.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-frapea-motion/motion.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-frapea-motion/motion.json
- HTML version of this page: https://verifymcp.io/servers/com-frapea-motion/motion