Is the Frapea Motion MCP server down?

mcp-registry/com.frapea/motion · v0.1.0

As of 2026-10-19 20:47 UTC, the Frapea Motion MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

claude mcp add --transport http frapea-motion-mcp-server https://motion.frapea.com/mcp

{
  "mcpServers": {
    "frapea-motion-mcp-server": {
      "type": "http",
      "url": "https://motion.frapea.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (73/100)

What to fix (4)

Auto-fix: 13 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.frapea%2Fmotion/fixes

{
  "name": "check_playback",
  "description": "PLAY IT THROUGH. Puts the composition on the user's stage and plays it from frame 0 through the real preview — the path a person watches, which inspect_composition does not take — from the first frame to the last. Buffering is fine; any error ends it. Answers within about 20 s: {status:\"running\", at, total} means call again with the same id to keep waiting (it continues the same run). Then {status:\"done\", verdict:\"ok\"|\"problems\", problems, warnings} or {status:\"incomplete\", reason} — hidden (ask",
  "inputSchema": {
    "type": "object",
    "required": [
      "token"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Omit for the active one."
      },
      "token": {
        "type": "string",
        "description": "The session token that connect returned."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "close_composition",
  "description": "Closes a composition and removes it from the user's tabs. Use it to clear up attempts you made along the way — an agent that leaves ten of them behind has handed the user the tidying. Needs an explicit id; it will never guess the active one.",
  "inputSchema": {
    "type": "object",
    "required": [
      "token",
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "The composition to close. Required."
      },
      "token": {
        "type": "string",
        "description": "The session token that connect returned."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}

{
  "name": "create_composition",
  "description": "Writes a new composition and opens it as a tab in front of the user. `files` maps path to TSX source and must include the entry (default composition.tsx). Read read_skill {topic:'motion'} and {topic:'motion-craft'} first — this API is not guessable and the craft guide is what stops the result looking generated. Aim well beyond a slide deck. With UI-like parts, write them in their own file with a partsBoard prop (default false) and check the board before building scenes.",
  "inputSchema": {
    "type": "object",
    "required": [
      "token",
      "name",
      "width",
      "height",
      "fps",
      "durationInFrames",
      "files"
    ],
    "properties": {
      "fps": {
        "type": "number"
      },
      "name": {
        "type": "string"
      },
      "entry": {
        "type": "string",
        "description": "Defaults to composition.tsx."
      },
      "files": {
        "type": "object",
        "additionalProperties": {
          "type": "string"
        }
      },
      "token": {
        "type": "string",
        "description": "The session token that connect returned."
      },
      "width": {
        "type": "number"
      },
      "height": {
        "type": "number"
      },
      "schema": {
        "type": "object",
        "description": "Props schema; drives the editable controls."
      },
      "durationInFrames": {
        "type": "number"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.frapea/motion"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.frapea/motion"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~3,672 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• tell_user ~346 tokens
• create_composition ~312 tokens
• put_media ~284 tokens
• inspect_composition ~271 tokens
• get_problems ~248 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.frapea%2Fmotion.svg)](https://glimind.com/server/mcp-registry%2Fcom.frapea%2Fmotion?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.frapea%2Fmotion?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.frapea%2Fmotion.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.frapea%2Fmotion.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.frapea%2Fmotion?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:32bb27b52a6ab55e…, first seen 2026-10-17, included at leaf 1780 of 28,727. Version history · verify what your client received.

Tools (19)

• check_playback
• close_composition
• connect
• create_composition
• create_session
• get_composition
• get_media
• get_problems
• inspect_composition
• inspect_media
• list_compositions
• list_media
• organize_media
• put_media
• read_skill
• set_props
• tell_user
• update_composition
• wait_for_tab

Compare: most reliable media servers · most reliable files servers · most reliable knowledge servers · most reliable communication servers · most reliable browser servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Frapea Motion MCP server down right now?

As of 2026-10-19 20:47 UTC, the Frapea Motion MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Frapea Motion MCP server provide?

Frapea Motion MCP server advertises 19 tools, including check_playback, close_composition, connect, create_composition, create_session.

How do I install Frapea Motion MCP server?

Point your MCP client at this streamable-http endpoint: https://motion.frapea.com/mcp

Is the Frapea Motion MCP server safe to connect to an AI agent?

Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Frapea Motion MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.