MCP servers › io.github.feimacode › open-design

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.feimacode/open-design

Design skills, design systems and artifact tools: landing pages, decks, prototypes, posters, more. — the publisher's description

7 of 9 record checks metRead-only · tools listed 2026-10-23Topic: media-and-design · AI-classifiedversion 0.2.0HTMLMITstandard input/output23 tools

Summary

io.github.feimacode/open-design is a local MCP server listed in the official MCP registry at version 0.2.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 23 tools, 0 resources and 201 prompts.

Record checks

7 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#2,347 of 15,112 packages by monthly downloads
Not ranked by stars: 4 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 23
Described as changing data: 18 of 23 toolsAI-classified
Mainly works on: files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic: media-and-designAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

18 tools are described as changing something (read_open_design_source, prepare_open_design_brief, prepare_open_design_exploration, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 0.2.0, published 2026-10-10 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-10 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.2.0 (published 2026-10-10).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

23tools

0resources

201prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

18 of 23 tools are described as changing something (creating, editing, deleting, sending or running).

list_open_design_skillsreads or searches
“Lists available Open Design skills, design templates, and remixable examples — reusable design-task recipes, rendering styles, and (for 'example' entries) actual starting artifacts bundled with this …”
5 inputs
- querystring“Optional free-text filter, matched against skill name, description, and triggers.”
- modestring“Optional exact mode filter.”
- sourcestring“Optional exact source filter.”
- surfacestring“A kind of thing to make — returns that surface's entries in curated order (the recipe first, then its remixable example; never catalog stubs), plus the surface…”
- remixableOnlyboolean“Optional: when true, only return entries with a non-empty exampleArtifactPath (i.e.”
list_open_design_design_systemsreads or searches
“Lists available Open Design design systems — brand-inspired visual token sets (palette, typography, spacing, component rules), each with a 'category' and an 'active' flag marking the current active d…”
2 inputs
- querystring“Optional free-text filter, matched against design system name, summary, and category.”
- categorystring“Optional exact category filter, e.g.”
read_open_design_sourcedescribed as changing data
“Converts a workspace document (DOCX, PPTX, XLSX, PDF, Markdown, text or CSV) into Markdown under the output directory's sources/ folder, extracts its embedded images, and returns an outline (headings…”
1 input, 1 required
- pathstringrequired“Workspace-relative path of the document, e.g.”
prepare_open_design_briefgenerates contentdescribed as changing data
“Composes generation instructions for an Open Design artifact by combining the chosen skill's workflow, an optional design system's visual tokens, universal craft rules, and the user's brief.”
10 inputs, 2 required
- skillIdstringrequired“A skill id from list_open_design_skills, in its full 'od:<mode>:<name>' form.”
- designSystemIdstring“Optional design system id from list_open_design_design_systems.”
- briefstringrequired“The user's design brief / request, in their own words.”
- collectionIdstring“Set this (a slug you derive once from the collection name, reused verbatim on every call) when this artifact is one screen of a multi-screen design collection …”
- collectionNamestring“A short display name for the collection, e.g.”
- screenRolestring“Required together with collectionId — this screen's short role label, e.g.”
- screenTotalnumber“Optional: the total number of screens you've planned for this collection, for an accurate "screen N of M" framing.”
- sourcesarray“Workspace paths of documents to build the design from (1–10): reports, specs, spreadsheets, existing decks, or repository files such as CHANGELOG.md or docs/ad…”
- formatstring“Optional canvas format.”
- fluidboolean“With format (or alone): build a fluid design that reflows to any canvas shape, sized in container units with layout rules for wide and tall shapes; the shape i…”
prepare_open_design_explorationgenerates contentdescribed as changing data
“Use INSTEAD of prepare_open_design_brief when the user explicitly asks for options, directions, alternatives or several versions of a design.”
7 inputs, 2 required
- skillIdstringrequired“A skill id from list_open_design_skills, in its full 'od:<mode>:<name>' form.”
- briefstringrequired“The user's design brief / request, in their own words.”
- countinteger“How many directions: 2–4, default 3; for the style-tile skill 2–6, default 4.”
- axisstring“What the directions differ in.”
- directionIdsarray“Optional: pick specific directions instead of the default order.”
- customDirectionsarray“For a user-named axis (e.g.”
- designSystemIdstring“Optional design system id.”
compare_open_design_explorationreads or searchesdescribed as changing data
“Call after registering an exploration's directions.”
2 inputs, 1 required
- explorationIdstringrequired“The explorationId returned by prepare_open_design_exploration.”
- contactSheetboolean“Also render the comparison page to exports/contact-sheet.png.”
choose_open_design_directioncreates or changes datadescribed as changing data
“Call when the user picks a direction from an exploration.”
5 inputs, 3 required
- explorationIdstringrequired“The exploration id.”
- directionIdstringrequired“The chosen direction id.”
- nextstringrequired“What to do with the chosen direction.”
- notesstring“Optional: the user's own adjustments, in their words.”
- mergeFromarray“Required for 'merge': which aspects to take from which other directions.”
register_open_design_artifactcreates or changes datadescribed as changing data
“Call this AFTER you have written an artifact's entry file (and any supporting files) into the workspace with your normal file-editing tools.”
14 inputs, 3 required
- entryPathstringrequired“Workspace-relative path to the artifact's entry file.”
- kindstringrequired“The kind of artifact.”
- titlestringrequired“A short human-readable title for the artifact.”
- supportingFilesarray“Workspace-relative paths to sibling files the entry depends on, relative to the entry file's directory.”
- sourceSkillIdstring“The skillId used to generate this artifact, if any.”
- designSystemIdstring“The designSystemId used to generate this artifact, if any.”
- collectionIdstring“The same collectionId passed to prepare_open_design_brief, if this screen is part of a design collection.”
- collectionNamestring“The same collectionName passed to prepare_open_design_brief, if this screen is part of a design collection.”
- screenIndexnumber“0-based position of this screen within its collection (0 for the first screen, 1 for the second, ...).”
- screenRolestring“The same screenRole passed to prepare_open_design_brief, if this screen is part of a design collection.”
- explorationIdstring“The explorationId from prepare_open_design_exploration, if this artifact belongs to a design exploration.”
- directionIdstring“The direction's directionId, for an exploration sketch.”
- sourcesarray“The same source document paths passed to prepare_open_design_brief.”
- formatstring“The canvas format passed to prepare_open_design_brief (or the adaptation's registerArgs), if any.”
get_open_design_artifactreads or searches
“Reads back a registered Open Design artifact: its manifest, entry file content, supporting file list, and any open comments.”
1 input, 1 required
- entryPathstringrequired“Workspace-relative path to the artifact's entry file.”
set_active_design_systemcreates or changes datadescribed as changing data
“Sets (or clears, if designSystemId is omitted/empty) the active Open Design design system, persisted for this workspace.”
1 input
- designSystemIdstring“A design system id from list_open_design_design_systems.”
create_open_design_design_systemgenerates contentdescribed as changing data
“Composes instructions for authoring a brand-new, custom design system as a DESIGN.md file plus a sibling tokens.css following the Open Design token contract.”
4 inputs
- namestring“A short name for the design system.”
- briefstring“A description of the brand, in the user's own words.”
- sourceUrlstring“Optional: a website URL to extract a starting palette/fonts from.”
- existingDesignSystemIdstring“Optional: the id of an existing custom design system (user:…).”
port_open_design_artifact_to_appgenerates contentdescribed as changing data
“Composes instructions for porting a finished Open Design artifact's design into this workspace's actual, existing application as real, idiomatic production code.”
3 inputs, 1 required
- entryPathstringrequired“The workspace-relative path of the artifact to promote.”
- targetComponentPathstring“Optional: where the new component/code file should be written.”
- referenceComponentPathstring“Optional: an existing component file to use as the pattern reference.”

Show 11 more tools

pull_open_design_figma_framegenerates contentdescribed as changing data
“Composes instructions for translating a Figma frame into a real code artifact with 1:1 visual fidelity.”
2 inputs, 1 required
- figmaUrlstringrequired“A Figma frame URL, e.g.”
- designSystemIdstring“Optional design system id from list_open_design_design_systems to align the translated code with.”
remix_open_design_examplecreates or changes datadescribed as changing data
“Copies a curated Open Design example artifact (identified by its skillId, which must have a non-empty 'exampleArtifactPath') into the workspace as a starting point, registers it, and returns instruct…”
1 input, 1 required
- skillIdstringrequired“A skillId whose 'exampleArtifactPath' is non-empty.”
export_open_design_artifactgenerates contentdescribed as changing data
“Renders a registered Open Design artifact in a headless browser (an installed Chrome, Edge, or Chromium) and writes upload-ready file(s) under the artifact's own exports/ folder.”
28 inputs, 1 required
- entryPathstringrequired“Workspace-relative path to the registered artifact's entry file.”
- formatstring“Output format.”
- qualityinteger“JPEG quality (jpeg only).”
- widthinteger“Width in CSS pixels, given with height.”
- heightinteger“Viewport height in CSS pixels.”
- scalenumber“Device scale factor (1–3).”
- selectorstring“CSS selector; each matching element is exported as its own numbered image (e.g.”
- maxBytesinteger“Per-file byte budget; over-budget images are re-encoded as progressively lower-quality JPEG until they fit.”
- deckboolean“Force deck handling (true) or page handling (false).”
- slidesarray“Decks only: 1-based slide numbers to export, e.g.”
- badgeboolean“standalone/site only: add a small, closeable "Made with Open Design" footer badge.”
- targetstring“format "paste" only: where it will be pasted.”
- baseUrlstring“site: the https address the bundle will be served from, so the link-preview image (og:image) can be an absolute URL.”
- presetstring“A canvas format id instead of hand-copied sizes.”
- bleednumber“Print PDFs only: bleed in mm on every side.”
- cropMarksboolean“Print PDFs only: add crop marks at the trim corners in a 10 mm slug around the page.”
- checkOnlyboolean“Run the page load and preflight checks only, writing no files and leaving the manifest alone.”
- datastring“Workspace-relative CSV, XLSX or JSON-array file.”
- sheetstring“XLSX data only: the sheet to read (default: the first).”
- nameFieldstring“With data: the column whose value names each row's file (slugified, made unique), e.g.”
- splitboolean“With data and a PDF format: one PDF per row instead of one multi-page PDF.”
- presetsarray“Fluid designs only: export several canvas shapes in one call, each reflowed and preflighted at its own shape and written as <name>-<format>.<ext> (PDF for prin…”
- shapeSheetboolean“Fluid designs only: also write exports/<name>-shapes.png, one image showing the design at every shape in presets (default: all catalog formats), each labelled …”
- fpsinteger“mp4/webm/gif only: frames per second.”
- durationnumber“mp4/webm/gif only: length in seconds.”
and 3 more not listed here.
add_open_design_diagram_runtimecreates or changes datadescribed as changing data
“Adds the diagram runtime to a diagram's HTML entry file, or updates it in place: one inline <script data-od-runtime="diagram"> block, placed before </body>, that lays the diagram out in the browser.”
1 input, 1 required
- entryPathstringrequired“Workspace-relative path to the diagram's HTML entry file.”
list_open_design_integrationsreads or searches
“Looks up trusted third-party MCP servers (Canva, Figma, Notion, Google Drive, Slack, posting services such as Buffer and Metricool, X's official server) that a workflow step can use instead of a manu…”
4 inputs
- capabilitystring“What the step needs, e.g.”
- integrationstring“A specific integration id, e.g.”
- platformstring“Social network, for social.* capabilities: x, linkedin, instagram, facebook, threads, tiktok, youtube, pinterest, bluesky, mastodon.”
- agentstring“Which agent the setup steps are for.”
check_open_design_artifactreads or searches
“Renders a registered Open Design artifact in a headless browser (an installed Chrome, Edge, or Chromium) and returns what it looks like: screenshots attached as images, plus preflight findings (overf…”
5 inputs, 1 required
- entryPathstringrequired“Workspace-relative path to the registered artifact's entry file.”
- viewportsarray“Pages without a card only: 1–4 viewports to check instead of the default desktop 1440×900 and mobile 390×844.”
- slidesarray“Decks only: 1-based slide numbers to check (default every slide; the contact sheet shows the first 12 of them).”
- atarray“Animations: up to 6 times in seconds.”
- maxImagesinteger“How many screenshots to attach (default 3).”
adapt_open_design_artifactgenerates contentdescribed as changing data
“Re-composes a finished, registered design for other canvas formats: the same message, copy hierarchy and design system, laid out again for each new size rather than scaled.”
3 inputs, 2 required
- entryPathstringrequired“Workspace-relative path to the registered master design's entry file.”
- formatsarrayrequired“1–6 target canvas formats.”
- notesstring“Optional: what the user said about the adaptations (e.g.”
create_open_design_qr_codegenerates contentdescribed as changing data
“Generates a real, scannable QR code offline as SVG and saves it in a registered artifact's assets/ folder (listed in its manifest's supportingFiles), returning inline SVG markup to paste into the des…”
5 inputs, 2 required
- entryPathstringrequired“Workspace-relative path to the registered artifact the code belongs to.”
- textstringrequired“What the code encodes, usually a full https URL.”
- namestring“File name for the SVG under assets/ (default "qr"), e.g.”
- errorCorrectionstring“Error correction level.”
- margininteger“Quiet zone in modules (default 4, the standard; don't go below 2).”
publish_open_design_artifactmanages infrastructuredescribed as changing data
“Publishes a registered Open Design artifact as a live web page, so the user can share a link with teammates or stakeholders.”
5 inputs, 1 required
- entryPathstringrequired“Workspace-relative path to the registered artifact's entry file.”
- providerstring“Where to publish.”
- badgeboolean“Add the small, closeable "Made with Open Design" footer badge to the published page.”
- includeFilesarray“Workspace paths of files in this artifact's own exports/ folder (e.g.”
- publishedobject“Record mode: what the deploy reported.”
publish_open_design_artifact_to_canvagenerates contentdescribed as changing data
“Gets a finished Open Design artifact into Canva.”
1 input, 1 required
- entryPathstringrequired“The workspace-relative path of the artifact to get into Canva (as passed to register_open_design_artifact).”
push_open_design_artifact_to_figmagenerates contentdescribed as changing data
“Pushes a finished Open Design artifact into Figma as editable layers through the user's Figma MCP server.”
2 inputs, 1 required
- entryPathstringrequired“The workspace-relative path of the artifact's entry file (as passed to register_open_design_artifact).”
- refreshboolean“Re-capture the artifact even when a capture newer than the file exists (for example after changing assets the capture can't see).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 23 tools
Says what it returns: 74% of 23 tools
States limits, defaults or errors: 13% of 23 tools
Says when to use it: 100% of 23 tools
Items covered per tool: 2.9 of 4 on average

Counted from the listing

Parameters with a description: 100% of 112
Tools with a description: 100% of 23
Typical description length: 831 characters

The tool set

Counted from the listing

Tools: 23
Size of the list: about 11,912 tokens for an agent to load (characters ÷ 4)
Naming: 23 of 23 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 23 of 23 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @feimacode/open-design-agent-kit-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "open-design": {
      "command": "npx",
      "args": [
        "-y",
        "@feimacode/open-design-agent-kit-mcp@0.2.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "open-design": {
      "command": "npx",
      "args": [
        "-y",
        "@feimacode/open-design-agent-kit-mcp@0.2.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "open-design": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@feimacode/open-design-agent-kit-mcp@0.2.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"open-design","type":"stdio","command":"npx","args":["-y","@feimacode/open-design-agent-kit-mcp@0.2.0"]}'

Claude Code

claude mcp add --transport stdio open-design -- npx -y @feimacode/open-design-agent-kit-mcp@0.2.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @feimacode/open-design-agent-kit-mcp@0.2.0

Optional settings the entry also lists (left out above): OPEN_DESIGN_FIGMA_TOKEN.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.2.0
Latest stable: 0.2.0
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-H8plk8hgwaU47uYum…
Signature: signed
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 1,111 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.2.0 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/feimacode/open-design-agent-kit	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.feimacode
GitHub owner: an organization (feimacode)
Build record: signed

Repository: github.com/feimacode/open-design-agent-kit
Stars: 4
Repository age: 31–90 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 9 record checks met

#2,347 of 15,112 packages by monthly downloads
Not ranked by stars: 4 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.feimacode/open-design

Answered from the data above

Is io.github.feimacode/open-design safe to install?

We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 18 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.feimacode/open-design been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.feimacode/open-design do?

It lists 23 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, manage infrastructure and generate content. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.feimacode/open-design change or delete data?

18 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.feimacode/open-design publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.2.0, the latest stable release on npm.

Where is the source code of io.github.feimacode/open-design?

In github.com/feimacode/open-design-agent-kit, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.leancoderkavy/premiere-proMCP for Adobe Premiere Proalso has tools that creates or changes data, generates content, reads or searchescompare with this one
io.github.ffroliva/gflow-cligflow-clialso has tools that creates or changes data, generates content, reads or searchescompare with this one
io.github.nirholas/threews-grokthree.ws for Grokalso has tools that creates or changes data, generates content, reads or searchescompare with this one
io.github.nirholas/threews-3d-studio-freethree.ws 3D Studio (free)also has tools that creates or changes data, generates content, reads or searchescompare with this one
io.github.KyaniteLabs/kinocutKinocutalso has tools that creates or changes data, generates content, reads or searchescompare with this one
io.github.KyaniteLabs/mcp-videomcp-videoalso has tools that creates or changes data, generates content, reads or searchescompare with this one

Active servers whose topic is also “media-and-design” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
3,949 msConnected after 0 redirects.
Read the inventory: 23 tools, 0 resources, 201 prompts.
14,976 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

media-and-design

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.

Programming language

HTML

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

1,111 downloads a month

package registry · 2026-10-23

Publisher signals

owner: an organization · repository age: 31–90 days · stars: 0–9 · build record: signed

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.feimacode/open-design: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.feimacode/open-design

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.feimacode/open-design)](https://protocolprobe.com/mcp/servers/io.github.feimacode/open-design)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology