io.github.gekkyo/animate-mcp
NPM · ANIMATE-MCP
MCP server for Adobe Animate: edit scripts, timelines and library, then publish and verify.
Available components
Last scanned (15 hours ago)
Scores higher than 49% of npm servers
Category Design and Media
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to gekkyo/animate-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability49
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 860 tokens (~215/item across 4 items; 4 tools + 0 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 Management0
- Stability check failed: the tool surface changed between 0.1.6 and 0.4.0: 8 tool removals, 0 breaking changes, 3 additions. See how to fix → Fail
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety92
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_readonly" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −20
- Malware scan: pass → unverified ▼ security
- Stability: 0.13 → fail ▼ security
- Tool coverage: 43% → 17% ▼ functional
- Schema quality: 155 → 215 ▼ functional
- Schema quality: good → fair functional
- Package version: 0.3.2 → 0.4.0 functional
- 16 Nov 26 +16
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.1 → 0.3.2 functional
- 15 Nov 26 0
- Malware scan: unverified → pass ▲ security
- Schema quality: 3473 → 4206 ▼ functional
- Schema quality: 3473 → 3899 ▼ functional
- Tool coverage: 38% → 43% ▲ functional
- Tool coverage: 38% → 47% ▲ functional
- Destructive annotations: 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "preflight_publish" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. functional
- Package version: 0.1.9 → 0.3.1 functional
- Package version: 0.1.9 → 0.2.0 functional
- 14 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 2052 → 3473 ▼ functional
- Schema quality: 2052 → 2986 ▼ functional
- Tool coverage: 38% → 45% ▲ functional
- Security disclosure: fail → pass ▲ functional
- Package version: 0.1.7 → 0.1.9 functional
- Package version: 0.1.7 → 0.1.8 functional
- 13 Nov 26 +3
- Schema quality: 1443 → 2052 ▼ functional
- Tool coverage: 25% → 38% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- Package version: 0.1.6 → 0.1.7 functional
- 12 Nov 26 74
First indexed and scored.
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 Nov 2026 · Analysed npm/animate-mcp@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | gekkyo/animate-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/gekkyo/animate-mcp/.github/workflows/publish.yml@refs/tags/v0.4.0 |
| Rekor log index | 3947919728 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:83f3ec0ccf59b42f131e5548f9ac9457d09941b49da851429a14f2b7c05ad603cca11cc020056117d0478fae162442fbc4a42f4f334808a3c532e21ab |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 33 |
| 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 →
execute_readonly ~33
Run a tool whose readOnlyHint is true.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
execute_write ~39
Run any tool whose readOnlyHint is not true; may modify documents or files.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
run_jsfl ~86
Execute arbitrary code as JSFL inside Adobe Animate; it may modify documents or files. Prefer dedicated tools for document, timeline, tween, library, and script operations, and use run_jsfl only as a last resort when they cannot accomplish the task.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Arbitrary JSFL source to execute in Adobe Animate; use only when dedicated tools cannot accomplish the task. |
No output schema declared.
No examples provided.
search_tools ~26
Find Animate tools by exact name or free-text query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.gekkyo/animate-mcp server?
io.github.gekkyo/animate-mcp runs locally as an npm package, launched with npx -y animate-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · animate-mcp
claude mcp add gekkyo-animate-mcp -- npx -y animate-mcp
What is the io.github.gekkyo/animate-mcp server?
io.github.gekkyo/animate-mcp is listed in the public MCP registry as io.github.gekkyo/animate-mcp. MCP server for Adobe Animate: edit scripts, timelines and library, then publish and verify. This page covers its npm package (animate-mcp).
Is the io.github.gekkyo/animate-mcp server safe to use?
io.github.gekkyo/animate-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.gekkyo/animate-mcp server expose?
io.github.gekkyo/animate-mcp exposes 4 tools: search_tools, execute_readonly, execute_write, run_jsfl. Their descriptions and schemas cost roughly 184 tokens of context every time the server is loaded.
Is the io.github.gekkyo/animate-mcp server still maintained?
io.github.gekkyo/animate-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 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 io.github.gekkyo/animate-mcp server under?
io.github.gekkyo/animate-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.gekkyo/animate-mcp server?
VerifyMCP ran 16 checks on io.github.gekkyo/animate-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.