MotionLint
NPM · MOTIONLINT · SCANNED SEP 21
Catch bad animations before they ship. Deterministic motion audit + vision-LLM design review.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security69
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects sharp 0.33.5, a direct dependency. A fixed version is available. View diagnostics → Fail
- Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 42 of 164 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 939 tokens (~156/item across 6 items; 5 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MotionLint MCP server?
MotionLint runs locally as an npm package, launched with npx -y motionlint. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · motionlint
claude mcp add bobaba99-motionlint -- npx -y motionlint
{
"mcpServers": {
"bobaba99-motionlint": {
"command": "npx",
"args": [
"-y",
"motionlint"
]
}
}
} {
"servers": {
"bobaba99-motionlint": {
"command": "npx",
"args": [
"-y",
"motionlint"
]
}
}
} codex mcp add bobaba99-motionlint -- npx -y motionlint
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bobaba99-motionlint": {
"type": "local",
"command": [
"npx",
"-y",
"motionlint"
],
"enabled": true
}
}
} openclaw mcp add bobaba99-motionlint --command npx --arg -y --arg motionlint
mcp_servers:
bobaba99-motionlint:
command: "npx"
args: ["-y", "motionlint"] {
"McpServers": {
"bobaba99-motionlint": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"motionlint"
]
}
}
} assistant mcp add bobaba99-motionlint -t stdio -c npx -a -y motionlint
{
"mcpServers": {
"bobaba99-motionlint": {
"command": "npx",
"args": [
"-y",
"motionlint"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/motionlint@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | node -e "console.error('\n [motionlint] One more step: install Playwright Chromium so capture works:\n npx playwright install chromium\n')" |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-f88m-g3jw-g9cj | high | yes | ||
| GHSA-rgj7-g3m4-5g8c | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 164 packages
| Packages resolved | 164 |
|---|---|
| Stale | 42 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_latest_report ~25
Return the most recent UX review report content.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
No output schema declared.
No examples provided.
review_flow ~374
Run a scripted user-flow review against a URL. Captures frame bursts after every interaction and asks the vision LLM to grade animation quality, missing transitions, loading-state feedback, choreography, smoothness, and flicker. Use this when the user asks about animations, interaction states, or whether a flow feels good — NOT for static design issues (use review_url for those).
| Name | Type | Req | Description |
|---|---|---|---|
| burst_fullpage | boolean | – | Use full-page captures in each burst frame (slower; for in-page scroll animations). Default viewport-only. |
| consistency | number | – | Self-consistency samples (1=off, 3=recommended for harder flows). Default 1. |
| model | string | – | Model override. |
| name | string | – | Human label for the flow (used in artifact filenames). Default: 'flow'. |
| preferences_path | string | – | Optional path to a markdown file with team motion preferences. Embedded into the prompt and the report's CC handoff block. |
| provider | string | – | LLM provider override (auto|ollama|anthropic|openai|google|mock). |
| record | boolean | – | Record the full Playwright video alongside the contact sheet. Default true. |
| spec_path | string | – | Alternative to `steps`: path to a flow spec JSON file. |
| steps | string | – | Inline DSL: semicolon-separated steps. Actions: navigate <path>, click <selector>, hover <selector>, type <selector>=<value>, press <key>, scroll <px>, wait <ms>, capture "<label>". e.g.: 'navigate /… |
| url | string | yes | Base URL for the flow (joined with each step's `navigate`). |
No output schema declared.
No examples provided.
review_routes ~124
Review multiple routes of an application.
| Name | Type | Req | Description |
|---|---|---|---|
| base_url | string | yes | – |
| format | string | – | – |
| max_findings | number | – | Keep only the top N findings per route, severity-ordered. |
| max_pr_annotations | number | – | SARIF only: emit at most N results per route report, severity-ordered. |
| model | string | – | – |
| new_only | boolean | – | Report only findings not seen in prior runs of each route. |
| provider | string | – | – |
| routes | array | yes | – |
| viewports | array | – | – |
No output schema declared.
No examples provided.
review_url ~212
Capture and analyze a URL for UI/UX issues using vision AI.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format (default: md). 'html' is a polished, shareable report. |
| max_findings | number | – | Keep only the top N findings, severity-ordered (agent focus). |
| max_pr_annotations | number | – | SARIF only: emit at most N results per report, severity-ordered (reviewer fatigue). |
| model | string | – | Model override. |
| new_only | boolean | – | Report only findings not seen in prior runs of the same URL. |
| provider | string | – | LLM provider override (auto|ollama|anthropic|openai|google|mock). |
| record | boolean | – | Record a video of the capture. |
| url | string | yes | URL to review. |
| viewports | array | – | Viewports to capture (default: mobile + desktop). |
| wait_for | string | – | CSS selector or 'networkidle' to wait for before capture. |
No output schema declared.
No examples provided.
tune_animations ~187
Detect every animation on a page (CSS transitions/keyframes plus Motion One / GSAP / anime.js / @formkit/auto-animate / lottie-web), and write an interactive HTML tuner page where the user can adjust duration/delay/easing live and export a Claude-Code-ready prompt with the parameter changes. Returns the file path of the generated tuner. Use when the user wants to fine-tune existing animation parameters, NOT to review for issues.
| Name | Type | Req | Description |
|---|---|---|---|
| output | string | – | Where to write the tuner HTML. Default .motionlint/tuner/index.html. |
| settle_ms | number | – | Time to wait after load for animations to register. Default 1500. |
| url | string | yes | URL to capture animations from. |
| viewport_height | number | – | Capture viewport height. Default 800. |
| viewport_width | number | – | Capture viewport width. Default 1280. |
No output schema declared.
No examples provided.
What is the MotionLint MCP server?
MotionLint is an MCP server listed in the public MCP registry as io.github.bobaba99/motionlint. Catch bad animations before they ship. Deterministic motion audit + vision-LLM design review. This page covers its npm package (motionlint).
Is the MotionLint MCP server safe to use?
MotionLint scores 73 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 September 2026. It declares an install script we flagged as high risk. 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 MotionLint MCP server expose?
MotionLint exposes 5 tools: review_url, review_routes, review_flow, tune_animations, get_latest_report. Their descriptions and schemas cost roughly 922 tokens of context every time the server is loaded.
Is the MotionLint MCP server still maintained?
MotionLint is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the MotionLint MCP server under?
MotionLint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.