# Motion Menu (remote · www.motionmenu.ca)

597 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. The entire library is free.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `www.motionmenu.ca`: 80/100 (this document), [markdown](https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp-2.md), [page](https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp-2)

## Channel facts

- Endpoint: `https://www.motionmenu.ca/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `16.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-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2082 tokens (~189/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Motion Menu MCP server?

Motion Menu is a hosted endpoint at https://www.motionmenu.ca/api/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 dev55acc-ai-motion-menu 'https://www.motionmenu.ca/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev55acc-ai-motion-menu": {
      "url": "https://www.motionmenu.ca/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev55acc-ai-motion-menu": {
      "type": "http",
      "url": "https://www.motionmenu.ca/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev55acc-ai-motion-menu]
url = "https://www.motionmenu.ca/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev55acc-ai-motion-menu": {
      "type": "remote",
      "url": "https://www.motionmenu.ca/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev55acc-ai-motion-menu --url 'https://www.motionmenu.ca/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev55acc-ai-motion-menu:
    url: "https://www.motionmenu.ca/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev55acc-ai-motion-menu": {
      "Transport": "http",
      "Url": "https://www.motionmenu.ca/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev55acc-ai-motion-menu -t streamable-http -u 'https://www.motionmenu.ca/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev55acc-ai-motion-menu": {
      "type": "http",
      "url": "https://www.motionmenu.ca/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-09-22 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 79, +1)

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

### 2026-09-18 (score 78, +1)

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

### 2026-09-15 (score 77, +1)

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

### 2026-09-13 (score 76, +1)

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

### 2026-09-11 (score 75, +1)

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

### 2026-09-10 (score 74, 0)

- [functional regression] Schema quality: 1838 → 2082
- [functional] New tool “propose_directions”
- [cosmetic] “build_page” added an optional parameter “direction_id”
- [cosmetic] “build_page” added an optional parameter “exclusions”
- [cosmetic] “build_page” added an optional parameter “history”
- [cosmetic] “build_page” added an optional parameter “seed”
- [cosmetic] “recommend_patterns” added an optional parameter “exclusions”
- [cosmetic] “recommend_patterns” added an optional parameter “history”
- [cosmetic] “recommend_patterns” added an optional parameter “seed”

### 2026-09-09 (score 74, +1)

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

## MCP tools (11)

### `list_patterns` (~271 tokens)

List Motion Menu patterns. Every row is "number  slug  <role>  [tags]  · title". ROLE is where the pattern goes on a page (hero, nav, pricing, background, product, form…) — filter by it when you are building a page rather than hunting an effect. The SLUG is the permanent identity — prefer it. Filter by tag (e.g. "scroll", "webgl", "seam", "commerce"), by collection slug (e.g. "seams-handoffs"), by free-text query, or by legacy section letter. Call with no arguments to see the whole catalogue and its tag vocabulary.

Input parameters:

- `collection` (string): optional collection slug, e.g. "webgl-3d"
- `query` (string): optional substring filter on title/description
- `role` (string): WHERE IT GOES on a page — hero, nav, footer, pricing, background, gallery, product, form, stats, testimonial, cta, content, seam, chrome, type. Start here when building a page.
- `section` (string): legacy section letter, e.g. "J" — tags supersede this
- `tag` (string): optional tag, e.g. "scroll", "glsl", "commerce"

### `get_pattern` (~118 tokens)

Get one pattern by number, including its complete transplantable HTML, CSS and JS. Pass framework to get a ready-to-use component wrapper (react .tsx, vue .vue, svelte .svelte, or vanilla .ts).

Input parameters:

- `framework` (string): component wrapper format (default: raw HTML/CSS/JS)
- `number` (string): pattern number, e.g. "84" — a permanent alias for the slug
- `slug` (string): permanent identity, e.g. "velocity-image-bend" — preferred

### `get_kit` (~47 tokens)

Get the Motion Menu build kit: the design laws, the one-page act protocol, stack pins, known gotchas, and the full pattern index. Call this FIRST before building a page.

### `get_design_digest` (~45 tokens)

Get the machine-readable Motion Menu quality contract. Call before build_page. It defines anti-generic composition rules, motion lifecycle, responsive requirements, truth constraints, and release verification gates.

### `check_updates` (~117 tokens)

Check whether patterns you already built with have changed. Pass the library version you last built against (from `version` in a previous check_updates or /p/manifest.json) and get back exactly which slugs were added, changed or removed — so you re-pull three patterns instead of all of them. Call with no arguments to read the current version and library counts. Record the version you get back alongside the code you generate.

Input parameters:

- `since` (string): The library version you built against. Omit to just read the current one.

### `recommend_patterns` (~293 tokens)

Intent-aware pattern recommendations. Describe what you are building — industry, style, mood, technical needs — and get scored results with reasons and compatibility suggestions. Returns metadata only (number, slug, title, role, score, reason, compatible_with). Call get_pattern to retrieve the actual code for any recommendation.

Input parameters:

- `context` (array): Slugs or numbers already chosen for this page (order does not matter here). Recommendations that clash with any of them are excluded, a pattern already at its own max_per_page in context is skipped,…
- `count` (number): Max results (default 5, max 20)
- `exclusions` (array): Pattern slugs or numbers that must not be returned.
- `history` (array): Recently used pattern slugs or numbers. They receive a strong cooldown penalty instead of dominating every session.
- `intent` (string, required): What you are building, e.g. "premium SaaS landing page for enterprise AI startup" or "dark minimal portfolio with dramatic 3D hero"
- `role` (string): Optional page-role filter (hero, nav, pricing, footer, background, etc.)
- `seed` (string|number): Reproducible creative seed. The same brief and seed return the same candidates; change it to explore another valid realization.

### `propose_directions` (~97 tokens)

Turn a business/page brief into three deliberately different design genomes before choosing components. Each direction defines layout grammar, typography, imagery, motion physics, density rhythm, and explicit avoid rules. Pass a returned direction_id into build_page with the same brief and seed.

Input parameters:

- `brief` (string, required): Business, audience, offer, conversion goal, real assets, and brand constraints.
- `seed` (string|number): Reproducible creative seed.

### `build_page` (~217 tokens)

Design a complete page from intent. Returns an act map — 5–7 acts in page order, each with a purpose, recommended patterns (by slug), and a density rating (loud/quiet). Follows the one-page protocol: density wave pacing, one GL spectacle, 12–18 viewport-heights. Feed the result straight to get_pattern to retrieve the code. Returns metadata only — no pattern bodies.

Input parameters:

- `acts` (number): Number of acts (default 6, range 5–7)
- `direction_id` (string): One direction_id returned by propose_directions for this same intent/seed.
- `exclusions` (array): Pattern slugs or numbers that must not be used.
- `history` (array): Recently used pattern slugs or numbers to cool down.
- `intent` (string, required): What the page is for, e.g. "luxury real estate landing page" or "SaaS startup launch with pricing"
- `seed` (string|number): Reproducible creative seed.

### `validate_combination` (~100 tokens)

Check whether a set of patterns work well together. Pass the slugs (or numbers) of patterns you plan to combine on a page and get a compatibility report: overall score, per-pair analysis, style/industry coherence, intensity balance, page-flow coverage, and warnings (duplicate roles, missing positions, too many heavy patterns). Call BEFORE building to catch mismatches early.

Input parameters:

- `components` (array, required): Pattern slugs or numbers to validate together

### `audit_page` (~229 tokens)

Audit an EXISTING page (yours or a client's — any AI builder, any stack) for the default-AI "section grammar" tell: numbered steps, a centered hero with two buttons, 3-up icon cards, a testimonial/FAQ/CTA-band skeleton repeating unchanged. Deterministic, no LLM — every finding cites the exact matched HTML. Returns an ai_shaped_score (0-100), per-section tells with evidence, page-level tells (skeleton order, uniform scaffolding, default type/motion), and prescriptions: real Motion Menu patterns to replace each flagged section, drawn from the same graph recommend_patterns/validate_combination use, plus the exact next tool calls to fetch and validate them. FREE, no key required.

Input parameters:

- `html` (string): the page's full HTML — one page per call; a multi-page site is the caller's own loop
- `url` (string): alternative to html — fetched server-side (https only, public addresses only, 3 MB cap, 10 s timeout, no redirect to a private range, no credentials forwarded)

### `verify_repair` (~158 tokens)

Re-audit a page you just rewrote from audit_page's prescriptions and get a pass/fail verdict: fresh ai_shaped_score, the delta from the prior audit (pass baseline_score or the whole prior audit_page result as `baseline`), and any tells STILL present, each with a concrete fix instruction. FREE, no key required.

Input parameters:

- `baseline` (object): optional — the whole prior audit_page result, for a per-section tell-count delta in addition to the overall score delta; baseline_score is derived from it if omitted
- `baseline_score` (number): optional — the ai_shaped_score from the prior audit_page call, for a pass/fail delta
- `html` (string, required): the rewritten page's full HTML

## Diagnostics

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

## Score history

- 2026-09-24: 80
- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 71
- 2026-09-03: 71
- 2026-09-02: 70
- 2026-09-01: 70
- 2026-08-31: 70
- 2026-08-30: 69
- 2026-08-29: 69
- 2026-08-28: 68
- 2026-08-27: 68
- 2026-08-26: 67

## Common questions

### What is the Motion Menu MCP server?

Motion Menu is an MCP server listed in the public MCP registry as io.github.dev55acc-ai/motion-menu. 597 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. The entire library is free. This page covers its hosted endpoint (https://www.motionmenu.ca/api/mcp).

### Is the Motion Menu MCP server safe to use?

Motion Menu scores 80 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 Menu MCP server expose?

Motion Menu exposes 11 tools: list_patterns, get_pattern, get_kit, get_design_digest, check_updates, and 6 more. Their descriptions and schemas cost roughly 1,692 tokens of context every time the server is loaded.

### Does the Motion Menu MCP server require authentication?

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

### Is the Motion Menu MCP server still maintained?

Motion Menu is still listed as active in the MCP registry. We last reached this channel on 24 September 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://www.motionmenu.ca/api/mcp
- Website: https://www.motionmenu.ca/
- Changelog RSS feed: https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp-2