# Motion Menu (remote · motion-menu-two.vercel.app)

596 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. Free tier + $149 lifetime.

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

## Components

- remote · `motion-menu-two.vercel.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp.md), [page](https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp)

## Channel facts

- Endpoint: `https://motion-menu-two.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `14.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-08-19.

- **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 13 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2415 tokens (~185/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev55acc-ai-motion-menu https://motion-menu-two.vercel.app/api/mcp
```

### Codex

```toml
[mcp_servers.dev55acc-ai-motion-menu]
url = "https://motion-menu-two.vercel.app/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add dev55acc-ai-motion-menu --url https://motion-menu-two.vercel.app/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev55acc-ai-motion-menu:
    url: "https://motion-menu-two.vercel.app/api/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev55acc-ai-motion-menu": {
      "type": "http",
      "url": "https://motion-menu-two.vercel.app/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-08-19 (score 69, +1)

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

### 2026-08-18 (score 68, +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-08-15 (score 67, +1)

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

### 2026-08-13 (score 66, +1)

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

### 2026-08-12 (score 65, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1930 → 2415
- [functional] New tool “audit_page”
- [functional] New tool “verify_repair”

### 2026-08-11 (score 65, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 63)

First indexed and scored.

## MCP tools (13)

### `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` (~190 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). Pass theme (e.g. "daf", "wb", "blmedia" — see list_themes) to receive the bundle ALREADY re-skinned: themed :root tokens prepended and every known JS/GLSL color literal rewritten. No color work needed on your side.

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
- `theme` (string): optional theme name — call list_themes

### `list_themes` (~27 tokens)

List available Motion Menu themes (name, mode, label) for get_pattern/get_theme.

### `get_theme` (~88 tokens)

Get one theme: token values, font stacks, ready-to-paste :root CSS block, and the literal→color substitution map for theming code by hand (exact strings: hex, 0x numbers, "r,g,b" triplets, GLSL vec3). Build/tune themes at /theme.html.

Input parameters:

- `name` (string, required): theme name, e.g. "daf"

### `compose_page` (~310 tokens)

Compose a complete standalone working page from Motion Menu patterns — OR, given a `brief` instead of `sections`, get back a structured COMPOSITION PLAN (pattern picks with reasons, no HTML) reasoned over the pattern graph: role fit, pairs_with affinity, clashes checked across the whole plan, max_per_page/placement enforced by construction (one spectacle max, heavy never early, footer terminal). A plan can never contain a violation validate_combination would also reject — same rule engine, checked before each pick. Give explicit `sections` (pattern numbers in page order) and a theme instead to get back one self-contained HTML document with the scroll spine, shared runtime, page-level chrome, and all pattern code already themed. Both modes require the compose entitlement (Lifetime plan) and design_digest_version: 1 so the anti-generic quality contract is explicit. Per-section "swap" (sections mode only) replaces literal text strings (find→replace) to put real copy in.

Input parameters:

- `brief` (object): Compose from intent instead of an explicit section list — returns a JSON composition plan, not built HTML. Mutually exclusive with `sections`.
- `design_digest_version` (number, required): Required acknowledgement that get_design_digest was read (currently 1).
- `name` (string): page title
- `sections` (array): page sections in order (omit and pass `brief` instead for a composition plan)
- `theme` (string): theme name (list_themes) — default "mm"

### `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` (~48 tokens)

Get the machine-readable Motion Menu quality contract. Call before build_page or compose_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` (~217 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)
- `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.)

### `build_page` (~149 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 compose_page or get_pattern to retrieve the code. Returns metadata only — no pattern bodies.

Input parameters:

- `acts` (number): Number of acts (default 6, range 5–7)
- `intent` (string, required): What the page is for, e.g. "luxury real estate landing page" or "SaaS startup launch with pricing"

### `validate_combination` (~101 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 compose_page 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#diagnostics

## Score history

- 2026-08-19: 69
- 2026-08-18: 68
- 2026-08-17: 67
- 2026-08-16: 67
- 2026-08-15: 67
- 2026-08-14: 66
- 2026-08-13: 66
- 2026-08-12: 65
- 2026-08-11: 65
- 2026-08-10: 63

## Links

- Remote endpoint: https://motion-menu-two.vercel.app/api/mcp
- Website: https://motion-menu-two.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev55acc-ai-motion-menu/api-mcp