io.github.CloudCorpRecords/designport
NPM · @RENETURCIOS/DESIGNPORT · 2 COMPONENTS
Figma REST API client: files, nodes, images, styles, components, projects and comments.
Available components
Last scanned (18 hours ago)
Scores higher than 34% 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 93 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 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 598 tokens (~59/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 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.
- 1 Nov 26 65
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 4 Nov 2026 · Analysed npm/@reneturcios/designport@0.1.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 →
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
get_comments ~36
Get the comments on a Figma file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | Figma file key identifying the file whose comments to return. |
No output schema declared.
No examples provided.
get_file ~79
Get a Figma file's document tree by file key.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | number | – | Optional depth of the document tree to return, as a number of levels. |
| file_key | string | yes | Figma file key identifying the file to retrieve. |
| version | string | – | Optional specific version of the file to retrieve, identified by its version ID. |
No output schema declared.
No examples provided.
get_file_components ~39
Get the components published in a Figma file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | Figma file key identifying the file whose published components to return. |
No output schema declared.
No examples provided.
get_file_nodes ~107
Get specific nodes from a Figma file by comma-separated node IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | number | – | Optional depth of the node subtrees to return, as a number of levels. |
| file_key | string | yes | Figma file key identifying the file containing the nodes. |
| node_ids | string | yes | Comma-separated list of node IDs to retrieve from the file. |
| version | string | – | Optional specific version of the file to read the nodes from, identified by its version ID. |
No output schema declared.
No examples provided.
get_file_styles ~39
Get the styles published in a Figma file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | Figma file key identifying the file whose published styles to return. |
No output schema declared.
No examples provided.
get_image_fills ~41
Get the image fills referenced by a Figma file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | Figma file key identifying the file whose image fills to return. |
No output schema declared.
No examples provided.
get_images ~102
Render nodes of a Figma file to image URLs in a format and scale.
| Name | Type | Req | Description |
|---|---|---|---|
| file_key | string | yes | Figma file key identifying the file containing the nodes to render. |
| format | string | – | Optional output format for the rendered images, such as png, jpg, svg, or pdf. |
| node_ids | string | yes | Comma-separated list of node IDs to render as images. |
| scale | number | – | Optional scale factor for the rendered images. |
No output schema declared.
No examples provided.
get_team_projects ~35
List the projects belonging to a Figma team.
| Name | Type | Req | Description |
|---|---|---|---|
| team_id | string | yes | Figma team ID whose projects to list. |
No output schema declared.
No examples provided.
list_project_files ~34
List the files in a Figma project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Figma project ID whose files to list. |
No output schema declared.
No examples provided.
post_comment ~86
Post a comment to a Figma file; client_meta is an optional JSON-string encoding an object.
| Name | Type | Req | Description |
|---|---|---|---|
| client_meta | string | – | Optional JSON-string encoding an object with client metadata for the comment, such as its position. |
| file_key | string | yes | Figma file key identifying the file to post the comment to. |
| message | string | yes | Text of the comment to post. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/designport MCP server?
io.github.CloudCorpRecords/designport runs locally as an npm package, launched with npx -y @reneturcios/designport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/designport
claude mcp add cloudcorprecords-designport -- npx -y @reneturcios/designport
What is the io.github.CloudCorpRecords/designport MCP server?
io.github.CloudCorpRecords/designport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/designport. Figma REST API client: files, nodes, images, styles, components, projects and comments. This page covers its npm package (@reneturcios/designport).
Is the io.github.CloudCorpRecords/designport MCP server safe to use?
io.github.CloudCorpRecords/designport scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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.CloudCorpRecords/designport MCP server expose?
io.github.CloudCorpRecords/designport exposes 10 tools: get_file, get_file_nodes, get_images, get_image_fills, get_file_styles, and 5 more. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/designport MCP server still maintained?
io.github.CloudCorpRecords/designport is still listed as active in the MCP registry. We last reached this channel on 4 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.CloudCorpRecords/designport MCP server under?
io.github.CloudCorpRecords/designport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.