# io.github.CloudCorpRecords/designport (oci · ghcr.io/cloudcorprecords/designport)

Figma REST API client: files, nodes, images, styles, components, projects and comments.

- Trust score: 42/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/designport`: 66/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-designport/reneturcios-designport.md), [page](https://verifymcp.io/servers/cloudcorprecords-designport/reneturcios-designport)
- oci · `ghcr.io/cloudcorprecords/designport`: 42/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-designport/ghcr-io-cloudcorprecords-designport.md), [page](https://verifymcp.io/servers/cloudcorprecords-designport/ghcr-io-cloudcorprecords-designport)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/designport`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 598 tokens (~59/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/designport MCP server?

io.github.CloudCorpRecords/designport runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/designport:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-designport -- docker run --rm -i ghcr.io/cloudcorprecords/designport:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-designport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/designport:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-designport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/designport:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-designport -- docker run --rm -i ghcr.io/cloudcorprecords/designport:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-designport": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/designport:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-designport:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/designport:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-designport": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/designport:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-designport": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/designport:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 42, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 41, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 40)

First indexed and scored.

## MCP tools (10)

### `get_file` (~79 tokens)

Get a Figma file's document tree by file key.

Input parameters:

- `depth` (number): Optional depth of the document tree to return, as a number of levels.
- `file_key` (string, required): Figma file key identifying the file to retrieve.
- `version` (string): Optional specific version of the file to retrieve, identified by its version ID.

### `get_file_nodes` (~107 tokens)

Get specific nodes from a Figma file by comma-separated node IDs.

Input parameters:

- `depth` (number): Optional depth of the node subtrees to return, as a number of levels.
- `file_key` (string, required): Figma file key identifying the file containing the nodes.
- `node_ids` (string, required): 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.

### `get_images` (~102 tokens)

Render nodes of a Figma file to image URLs in a format and scale.

Input parameters:

- `file_key` (string, required): 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, required): Comma-separated list of node IDs to render as images.
- `scale` (number): Optional scale factor for the rendered images.

### `get_image_fills` (~41 tokens)

Get the image fills referenced by a Figma file.

Input parameters:

- `file_key` (string, required): Figma file key identifying the file whose image fills to return.

### `get_file_styles` (~39 tokens)

Get the styles published in a Figma file.

Input parameters:

- `file_key` (string, required): Figma file key identifying the file whose published styles to return.

### `get_file_components` (~39 tokens)

Get the components published in a Figma file.

Input parameters:

- `file_key` (string, required): Figma file key identifying the file whose published components to return.

### `get_team_projects` (~35 tokens)

List the projects belonging to a Figma team.

Input parameters:

- `team_id` (string, required): Figma team ID whose projects to list.

### `list_project_files` (~34 tokens)

List the files in a Figma project.

Input parameters:

- `project_id` (string, required): Figma project ID whose files to list.

### `get_comments` (~36 tokens)

Get the comments on a Figma file.

Input parameters:

- `file_key` (string, required): Figma file key identifying the file whose comments to return.

### `post_comment` (~86 tokens)

Post a comment to a Figma file; client_meta is an optional JSON-string encoding an object.

Input parameters:

- `client_meta` (string): Optional JSON-string encoding an object with client metadata for the comment, such as its position.
- `file_key` (string, required): Figma file key identifying the file to post the comment to.
- `message` (string, required): Text of the comment to post.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-designport/ghcr-io-cloudcorprecords-designport#diagnostics

## Score history

- 2026-11-05: 42
- 2026-11-04: 42
- 2026-11-03: 41
- 2026-11-02: 41
- 2026-11-01: 40

## Common questions

### 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 container image (ghcr.io/cloudcorprecords/designport).

### Is the io.github.CloudCorpRecords/designport MCP server safe to use?

io.github.CloudCorpRecords/designport scores 42 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 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 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.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.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/designport
- Repository: https://github.com/CloudCorpRecords/designport
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-designport/ghcr-io-cloudcorprecords-designport.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-designport/ghcr-io-cloudcorprecords-designport.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-designport/ghcr-io-cloudcorprecords-designport