Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.kendall8388/keyframe

NPM · KEYFRAME-MCP

Animate 2D skeletons in Keyframe.it, pixel sprites in Sprite Puppeteer, 3D rigs in MeshForge.

Available components

0 this week 75 Trust /100

Last scanned (10 hours ago)

Scores higher than 51% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 31 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3642 tokens (~56/item across 65 items; 65 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 2% 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 65 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 65 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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 →

Changelog

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.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 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.

  • 14 Oct 26 −3
    • Stability: pass → 0.80 functional
  • 13 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 5 Nov 2026 · Analysed npm/keyframe-mcp@0.6.0

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 →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 65 exposed · ~3,642 tokens

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 →

Tool Tokens
puppeteer_export ~96

Write an export to disk: sheet (PNG + Aseprite-style JSON), godot, unity, gm (GameMaker), frames (PNG zip), spine (rigged only), gif (one move) or project (.puppet.json). moves: current or all; dirs: view, 4 or 8.

NameTypeReqDescription
dirs–––
format–yes–
movestring––
moves–––

No output schema declared.

No examples provided.

puppeteer_list_projects ~21

List Sprite Puppeteer projects saved in this connector profile.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

puppeteer_load_image ~75

Load a sprite from the local disk as a new rigged character (PNG, GIF, WebP, JPEG, .aseprite/.ase or .psd; layers keep their names). The skeleton auto-fits; check with puppeteer_contact_sheet.

NameTypeReqDescription
namestring––
pathstringyes–

No output schema declared.

No examples provided.

puppeteer_methods ~33

List every Sprite Puppeteer scripting method with arguments, plus recipes. Reach methods without a named tool through puppeteer_call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

puppeteer_move_guide ~48

Rigged characters: pose channels with units, ranges and rest values, animation conventions, eases, events and the JSON shape for puppeteer_create_move. Read before creating a move.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

puppeteer_open ~77

Open Sprite Puppeteer (pixel-art sprite rigging, animation and play-testing) in the connector profile; optionally load a sample: "orc" or "knight" (sprite sheets: side, isometric, top-down) or "golem" (rigged). Returns the character state. Call first.

NameTypeReqDescription
sample–––

No output schema declared.

No examples provided.

puppeteer_open_project ~28

Open a saved Sprite Puppeteer project by ID.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

puppeteer_open_result ~31

Save and show Sprite Puppeteer in visible Chrome with the connector profile, so the user can keep working.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

puppeteer_play_move ~45

Show a move on the stage, optionally from a time or paused.

NameTypeReqDescription
movestringyes–
playboolean––
timenumber––

No output schema declared.

No examples provided.

puppeteer_render_frame ~59

One frame of a move as a PNG, transparent unless background:true.

NameTypeReqDescription
backgroundboolean––
frameinteger––
movestring––
scaleinteger––
timenumber––

No output schema declared.

No examples provided.

puppeteer_save ~28

Save the current character as a project, optionally naming it.

NameTypeReqDescription
namestring––

No output schema declared.

No examples provided.

puppeteer_screenshot ~26

Show the Sprite Puppeteer page. Prefer puppeteer_contact_sheet to judge motion.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

puppeteer_set_view ~92

Sprite sheets: camera set (side, iso8, topdown8, topdown4…) and direction (S = facing down). Rigged: drawn view (side, front, back, fq, bq). Both: facing 1 (right) or -1 (left).

NameTypeReqDescription
dir–––
facing–––
setstring––
viewstring––

No output schema declared.

No examples provided.

puppeteer_settings ~186

Change settings through the panel: background (checker is transparent in exports), fps, pixel scale, speed, exaggeration, effects, export format, one/all moves, 4/8 directions.

NameTypeReqDescription
bg–––
bonesboolean––
dirs–––
dummyboolean––
exportFxboolean––
facing–––
follownumber––
format–––
fpsinteger––
fxboolean––
glownumber––
hitStopnumber––
intensitynumber––
outline–––
overshootnumber––
rotsprite–––
scaleinteger––
smearboolean––
speednumber––
steppedboolean––
which–––

No output schema declared.

No examples provided.

puppeteer_state ~33

Current character: kind (rigged or sprite-sheet), moves, camera set and direction or views, settings, project.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.kendall8388/keyframe MCP server?

io.github.kendall8388/keyframe runs locally as an npm package, launched with npx -y keyframe-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 · keyframe-mcp

# add to Claude Code
claude mcp add kendall8388-keyframe -- npx -y keyframe-mcp
Common questions

What is the io.github.kendall8388/keyframe MCP server?

io.github.kendall8388/keyframe is an MCP server listed in the public MCP registry as io.github.kendall8388/keyframe. Animate 2D skeletons in Keyframe.it, pixel sprites in Sprite Puppeteer, 3D rigs in MeshForge. This page covers its npm package (keyframe-mcp).

Is the io.github.kendall8388/keyframe MCP server safe to use?

io.github.kendall8388/keyframe scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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.kendall8388/keyframe MCP server expose?

io.github.kendall8388/keyframe exposes 65 tools: keyframe_open, keyframe_methods, keyframe_call, keyframe_screenshot, keyframe_session, and 60 more. Their descriptions and schemas cost roughly 3,642 tokens of context every time the server is loaded.

Is the io.github.kendall8388/keyframe MCP server still maintained?

io.github.kendall8388/keyframe is still listed as active in the MCP registry. We last reached this channel on 5 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.kendall8388/keyframe MCP server under?

io.github.kendall8388/keyframe 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.kendall8388/keyframe MCP server?

VerifyMCP ran 15 checks on io.github.kendall8388/keyframe, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.kendall8388/keyframe: Security disclosure. 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.