FlipLetters
NPM · FLIPLETTERS-MCP-SERVER · 2 COMPONENTS
Draft, validate, render, and share split-flap and flip-dot board videos written in flipcode.
Available components
Last scanned (4 hours ago)
Scores higher than 46% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 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 21 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1225 tokens (~102/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 84% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +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.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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/flipletters-mcp-server@0.3.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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| 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 →
flipletters_example_board Example board ~97
Returns a complete, valid flipcode document for a board type (minimal, trainboard/station, artboard, flipdot, marquee, announcement, arena) — a known-good starting point to edit rather than writing from scratch.
| Name | Type | Req | Description |
|---|---|---|---|
| template | string | yes | Board type or alias: minimal, trainboard, station, artboard, art, flipdot, dots, marquee, desk, announcement, poster, arena, lightbox. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| template | string | yes | – |
No examples provided.
flipletters_flipcode_reference flipcode reference ~57
Returns the flipcode cheat sheet (spec v1): directives, board types and size limits, transition modes, and flip-native effect recipes. Call this before writing a board so the code you produce is valid on the first try.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | – |
No examples provided.
flipletters_list_postiz_destinations List Postiz share accounts on a project ~60
Lists Postiz destinations (masked keys) attached to a FlipLetters project. Use flipletters_list_workspaces first. Requires FLIPLETTERS_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | yes | Project id from flipletters_list_workspaces. |
No output schema declared.
No examples provided.
flipletters_list_postiz_integrations List channels on a Postiz destination ~62
Lists connected social channels for a project's Postiz share account. Use before flipletters_share_to_postiz to get integrationId. Requires FLIPLETTERS_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| destinationId | string | yes | – |
| workspaceId | string | yes | – |
No output schema declared.
No examples provided.
flipletters_list_teams List my teams ~41
Lists FlipLetters teams the API key owner belongs to (teamId, name, inviteCode). Requires FLIPLETTERS_API_KEY with team scope.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flipletters_list_workspaces List FlipLetters projects ~49
Lists agency projects (workspaces) for the API key owner, plus the active project id. Project-scoped keys return their bound project as active. Requires FLIPLETTERS_API_KEY.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
flipletters_render_board Cloud-render a board to MP4 ~142
Parses flipcode and submits a cloud MP4 render under the API key owner's FlipLetters plan (same free quota / Premium / Studio limits as the Studio). Requires FLIPLETTERS_API_KEY. Polls until done (or returns jobId if wait=false). Prefer share links for free previews; only render when the human wants an MP4 file.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Complete flipcode document. |
| repeat | integer | – | Loop the segment this many times (default 1). Caps apply for long / 4K exports. |
| wait | boolean | – | If true (default), poll until done/error. If false, return jobId immediately. |
No output schema declared.
No examples provided.
flipletters_render_status Cloud render job status ~46
Poll a cloud render job started with flipletters_render_board. Requires FLIPLETTERS_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id returned by flipletters_render_board. |
No output schema declared.
No examples provided.
flipletters_share_to_postiz Schedule export on Postiz ~234
Uploads a cloud media URL (or Studio host local fileName) to a project's Postiz destination and schedules/drafts/posts it. Loop: render_board → list_workspaces → list_postiz_destinations → list_postiz_integrations → share_to_postiz. Requires FLIPLETTERS_API_KEY. Prefer mediaUrl from flipletters_render_board.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Caption / post body. |
| date | string | yes | UTC ISO datetime, e.g. 2026-08-14T15:00:00.000Z |
| destinationId | string | yes | Postiz destination id on that project. |
| fileName | string | – | Local renders/*.mp4 name when Studio host has the file. |
| integrationId | string | yes | Postiz channel/integration id. |
| mediaUrl | string | – | HTTPS URL of the MP4 (from cloud render). |
| providerType | string | – | Postiz provider __type, e.g. tiktok, x, linkedin. |
| type | string | – | Default schedule. |
| workspaceId | string | yes | FlipLetters project id. |
No output schema declared.
No examples provided.
flipletters_share_to_team Share board to team library ~93
Parses flipcode and shares the board into a Team Library the key owner is a member of. Requires FLIPLETTERS_API_KEY. Use flipletters_list_teams first to get teamId.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Complete flipcode document. |
| name | string | yes | Display name for the template in the team library. |
| teamId | string | yes | Team id from flipletters_list_teams. |
No output schema declared.
No examples provided.
flipletters_template_url Readable template URL ~230
Builds a human-readable FlipLetters Studio URL where every query parameter mirrors one flipcode line — good for short text boards you want legible in the address itself (chat messages, docs). For full fidelity or paint grids use flipletters_validate_board's share link instead. Slides are strings with | between rows.
| Name | Type | Req | Description |
|---|---|---|---|
| accent | string | – | Hex color, # optional. |
| board | string | – | Board type/alias, e.g. "station". |
| flip | string | – | Transition, commas for spaces: "cascade,9,0.2,0.4". |
| grid | string | – | ROWSxCOLS, e.g. "8x34". |
| hold | string | – | Seconds, e.g. "6". |
| out | string | – | Canvas: "vertical", "square", "1200x630@25", … |
| slides | array | – | Each entry is one slide; | separates rows: "EGGS BENEDICT|FLAT WHITE". |
| sound | string | – | – |
| speed | string | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No examples provided.
flipletters_validate_board Validate a board ~114
Parses a flipcode document, returning the normalized canonical code, any warnings (out-of-range values are clamped, unknown lines ignored), a board summary, and links: a share URL that opens the exact board in the FlipLetters Studio, and an open-with-code URL that also reveals the code panel. Use this after drafting a board; fix warnings and re-validate until clean, then give the human the share link.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | A complete flipcode document (see flipletters_flipcode_reference). |
| Name | Type | Req | Description |
|---|---|---|---|
| canonicalCode | string | yes | – |
| openWithCodeUrl | string|null | yes | – |
| shareUrl | string|null | yes | Opens this exact board in the Studio. Null when the board is too large for a URL — share the code text instead. |
| summary | object | yes | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the FlipLetters MCP server?
FlipLetters runs locally as an npm package, launched with npx -y flipletters-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · flipletters-mcp-server
claude mcp add com-flipletters-mcp -- npx -y flipletters-mcp-server
What is the FlipLetters MCP server?
FlipLetters is an MCP server listed in the public MCP registry as com.flipletters/mcp. Draft, validate, render, and share split-flap and flip-dot board videos written in flipcode. This page covers its npm package (flipletters-mcp-server).
Is the FlipLetters MCP server safe to use?
FlipLetters scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 FlipLetters MCP server expose?
FlipLetters exposes 12 tools: flipletters_flipcode_reference, flipletters_validate_board, flipletters_example_board, flipletters_template_url, flipletters_render_board, and 7 more. Their descriptions and schemas cost roughly 1,225 tokens of context every time the server is loaded.
Is the FlipLetters MCP server still maintained?
FlipLetters 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 FlipLetters MCP server under?
FlipLetters declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.