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.

Keyframer

REMOTE · API.KEYFRAMER.DEV

150+ React Native animation recipes, scene authoring, phone preview via QR, Reanimated v4 codegen

0 this week 74 Trust /100

Last scanned (15 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Design and Media

Recent critical change

Authorization (24 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1293 tokens (~117/item across 11 items; 11 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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 (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • 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 hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Oct 26 0
    • HTTPS: fail → unverified ▼ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://api.keyframer.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=keyframer.dev CN=WE1,O=Google Trust Services,C=US 23 Oct 2026 21 Jan 2027 ECDSA 256 ECDSA-SHA256 3c195931a6e155eb0ecb14da937342b5
SANs: keyframer.dev, api.keyframer.dev, *.api.keyframer.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.keyframer.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
keyframer.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.keyframer.dev/mcp Verified 200
http (plaintext) http://api.keyframer.dev/mcp Inconclusive 405
MCP tools · 11 exposed · ~1,142 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
create_scene ~178

Save a scene and get an editor URL where it opens in the visual editor (timeline, canvas, node graphs, mobile QR preview). Validates first. Works without a key: the scene is then a public 24-hour guest scene with a scannable QR, kept forever by signing up (free) and pressing Remix. With a key it saves to the account (free accounts up to the free scene limit, paid unlimited).

NameTypeReqDescription
make_publicboolean–Make the scene publicly viewable — its share link (keyframer.dev/share/<id>) and QR then work for anyone, not just this account
namestring–Scene name shown in the editor (default "MCP scene")
scene–yesThe scene as a JSON object (preferred) or a JSON string. Call get_scene_format for the shape.

No output schema declared.

No examples provided.

generate_code ~161

Compile a scene into a runnable React Native component. Pass inline scene JSON or a scene_id from your account. Output targets Reanimated v4 by default ("animated" targets the RN core Animated API, reduced feature set). Deterministic — no AI, no credits. Requires an API key on a paid plan.

NameTypeReqDescription
apistring–Default "reanimated"
gesture_handler_versionstring–react-native-gesture-handler major (default v2)
relative_positioningboolean–Emit flex-relative layout instead of absolute coordinates
scene––The scene as a JSON object (preferred) or a JSON string. Call get_scene_format for the shape.
scene_idstring–Generate from a saved scene instead of inline JSON

No output schema declared.

No examples provided.

get_preview_qr ~89

A terminal-scannable QR code for a scene. Scan it with a phone camera and the scene runs live in the Keyframer preview app on real hardware — edits sync as they happen. Public scenes (including guest scenes) work without a key; private scenes need an API key on a paid plan.

NameTypeReqDescription
scene_idstringyesScene id from create_scene or list_scenes

No output schema declared.

No examples provided.

get_recipe ~114

Fetch one recipe by slug: metadata, the scene JSON (usable as a starting point for create_scene), and the generated React Native Reanimated component code. Recipe code is free to use.

NameTypeReqDescription
idstring–Alias for slug — a scene id from a recipe works too
include_codeboolean–Include generated code (default true)
scene_idstring–When a recipe has several scenes, pick one (defaults to the first)
slugstring–Recipe slug from search_recipes

No output schema declared.

No examples provided.

get_scene ~60

Fetch one of your scenes (or any public scene) as JSON — edit it and re-save with update_scene, or feed it to generate_code. Requires an API key.

NameTypeReqDescription
idstringyesScene id from list_scenes or an editor URL

No output schema declared.

No examples provided.

get_scene_format ~72

The Keyframer scene JSON format — read this before authoring a scene. Section "scene" covers elements/keyframes/easing; section "nodes" covers node graphs (procedural animation: clocks, springs, repeaters) with the full node-type schema.

NameTypeReqDescription
sectionstring–Default "scene"

No output schema declared.

No examples provided.

list_scenes ~33

List the scenes in the connected Keyframer account (id, name, updated, visibility). Requires an API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sample_scene ~139

Numerically preview a scene: evaluates keyframes AND node graphs at N evenly spaced times and returns each moving prop as a value series (the same math the editor preview runs). validate_scene checks structure — this checks MOTION: confirm ranges, spring overshoot, stagger offsets, and that elements actually move before create_scene. Free to call — iterate: author → sample → adjust.

NameTypeReqDescription
element_idsarray–Only report these element ids
samplesinteger–Sample count across the duration (default 9)
scene–yesThe scene as a JSON object (preferred) or a JSON string. Call get_scene_format for the shape.

No output schema declared.

No examples provided.

search_recipes ~98

Search 150+ free Keyframer recipes (bounce, carousels, progress rings, particles, text effects, shaders, scroll animations…). Each recipe has a scene + verified React Native Reanimated code. Returns slugs for get_recipe.

NameTypeReqDescription
categorystring––
limitinteger––
querystringyesWhat to build, e.g. "snap carousel with parallax" or "countdown ring"

No output schema declared.

No examples provided.

update_scene ~127

Replace the content of one of your scenes (full scene JSON, validated first) — the edit loop for iterating instead of duplicating. Live previews watching the scene update in place. Requires an API key; own scenes only.

NameTypeReqDescription
make_publicboolean–Change public visibility (unchanged if omitted)
namestring–New name (unchanged if omitted)
scene–yesThe scene as a JSON object (preferred) or a JSON string. Call get_scene_format for the shape.
scene_idstringyesScene id from create_scene or list_scenes

No output schema declared.

No examples provided.

validate_scene ~71

Validate a scene against the Keyframer format before create_scene or generate_code. Returns errors (must fix) and warnings (advisory). Free to call — iterate until clean.

NameTypeReqDescription
scene–yesThe scene as a JSON object (preferred) or a JSON string. Call get_scene_format for the shape.

No output schema declared.

No examples provided.

Install

How do I install the Keyframer MCP server?

Keyframer is a hosted endpoint at https://api.keyframer.dev/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.

remote · api.keyframer.dev

# add to Claude Code
claude mcp add --transport http dev-keyframer-keyframer 'https://api.keyframer.dev/mcp'
Common questions

What is the Keyframer MCP server?

Keyframer is an MCP server listed in the public MCP registry as dev.keyframer/keyframer. 150+ React Native animation recipes, scene authoring, phone preview via QR, Reanimated v4 codegen. This page covers its hosted endpoint (https://api.keyframer.dev/mcp).

Is the Keyframer MCP server safe to use?

Keyframer scores 74 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 Keyframer MCP server expose?

Keyframer exposes 11 tools: search_recipes, get_recipe, get_scene_format, validate_scene, sample_scene, and 6 more. Their descriptions and schemas cost roughly 1,142 tokens of context every time the server is loaded.

Does the Keyframer MCP server require authentication?

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

Is the Keyframer MCP server still maintained?

Keyframer 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 did VerifyMCP test on the Keyframer MCP server?

VerifyMCP ran 12 checks on Keyframer, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Keyframer: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.