figma-vault
NPM · FIGMA-VAULT · SCANNED SEP 25
Figma designs pulled once into a local vault; AI agents read them offline with no rate limits
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 671 tokens (~111/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the figma-vault MCP server?
figma-vault runs locally as an npm package, launched with npx -y figma-vault. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · figma-vault
claude mcp add nbhey-figma-vault -- npx -y figma-vault
{
"mcpServers": {
"nbhey-figma-vault": {
"command": "npx",
"args": [
"-y",
"figma-vault"
]
}
}
} {
"servers": {
"nbhey-figma-vault": {
"command": "npx",
"args": [
"-y",
"figma-vault"
]
}
}
} codex mcp add nbhey-figma-vault -- npx -y figma-vault
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nbhey-figma-vault": {
"type": "local",
"command": [
"npx",
"-y",
"figma-vault"
],
"enabled": true
}
}
} openclaw mcp add nbhey-figma-vault --command npx --arg -y --arg figma-vault
mcp_servers:
nbhey-figma-vault:
command: "npx"
args: ["-y", "figma-vault"] {
"McpServers": {
"nbhey-figma-vault": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"figma-vault"
]
}
}
} assistant mcp add nbhey-figma-vault -t stdio -c npx -a -y figma-vault
{
"mcpServers": {
"nbhey-figma-vault": {
"command": "npx",
"args": [
"-y",
"figma-vault"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.3 → 0.1.4 functional
- 23 Sept 26 71
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 25 Sept 2026 · Analysed npm/figma-vault@0.1.4
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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
vault_get_asset Design asset ~78
An image from the document by the path from node.asset.path (for example assets/logo.svg) or screenshot.png. Raster comes back as an image, svg as its source.
| Name | Type | Req | Description |
|---|---|---|---|
| docId | string | yes | Document id as returned by vault_list |
| path | string | yes | Path inside the document directory, for example assets/hero.png |
No output schema declared.
No examples provided.
vault_get_doc Whole document ~125
Normalized design tree together with its tokens. maxDepth cuts the tree by depth (0 — the root only); truncated nodes get childrenOmitted. Hidden nodes are not returned without includeHidden.
| Name | Type | Req | Description |
|---|---|---|---|
| docId | string | yes | Document id as returned by vault_list |
| includeHidden | boolean | – | Also return nodes hidden in Figma (hidden: true) — optional component slots. Defaults to false: building the screen as it looks does not need them. |
| maxDepth | integer | – | How many levels below the root to return. Omit for the whole tree. |
No output schema declared.
No examples provided.
vault_get_node Node subtree ~103
A node by id with all of its descendants. Use it instead of pulling the whole document.
| Name | Type | Req | Description |
|---|---|---|---|
| docId | string | yes | Document id as returned by vault_list |
| includeHidden | boolean | – | Also return nodes hidden in Figma (hidden: true) — optional component slots. Defaults to false: building the screen as it looks does not need them. |
| nodeId | string | yes | Node id in Figma format, for example 1:42 |
No output schema declared.
No examples provided.
vault_get_tokens Design system tokens ~42
Colors, text styles and effects of the document. Nodes refer to them via text.token.
| Name | Type | Req | Description |
|---|---|---|---|
| docId | string | yes | Document id as returned by vault_list |
No output schema declared.
No examples provided.
vault_list List designs ~26
Every exported document: docId, file and node name, export time, node count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vault_search Search the design ~120
Nodes whose name or text content contains the substring (case-insensitive). Returns id, type and the path from the root.
| Name | Type | Req | Description |
|---|---|---|---|
| docId | string | yes | Document id as returned by vault_list |
| includeHidden | boolean | – | Also return nodes hidden in Figma (hidden: true) — optional component slots. Defaults to false: building the screen as it looks does not need them. |
| limit | integer | – | Maximum number of hits, 50 by default |
| query | string | yes | Substring to look for in name and text.content |
No output schema declared.
No examples provided.
What is the figma-vault MCP server?
figma-vault is an MCP server listed in the public MCP registry as io.github.NBhey/figma-vault. Figma designs pulled once into a local vault; AI agents read them offline with no rate limits. This page covers its npm package (figma-vault).
Is the figma-vault MCP server safe to use?
figma-vault scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 figma-vault MCP server expose?
figma-vault exposes 6 tools: vault_list, vault_get_doc, vault_get_node, vault_search, vault_get_tokens, vault_get_asset. Their descriptions and schemas cost roughly 494 tokens of context every time the server is loaded.
Is the figma-vault MCP server still maintained?
figma-vault is still listed as active in the MCP registry. We last reached this channel on 25 September 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 figma-vault MCP server under?
figma-vault declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.