NVIDIA Elements
NPM · @NVIDIA-ELEMENTS/CLI · SCANNED SEP 21
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects adm-zip 0.6.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 95 of 288 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to NVIDIA/elements). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1462 tokens (~76/item across 19 items; 16 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability check failed: the tool surface changed between 2.1.10 and 2.2.3: 3 tool removals, 0 breaking changes, 1 additions. See how to fix → Fail
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% 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 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the NVIDIA Elements MCP server?
NVIDIA Elements runs locally as an npm package, launched with npx -y @nvidia-elements/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @nvidia-elements/cli
claude mcp add nvidia-elements -- npx -y @nvidia-elements/cli
{
"mcpServers": {
"nvidia-elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli"
]
}
}
} {
"servers": {
"nvidia-elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli"
]
}
}
} codex mcp add nvidia-elements -- npx -y @nvidia-elements/cli
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nvidia-elements": {
"type": "local",
"command": [
"npx",
"-y",
"@nvidia-elements/cli"
],
"enabled": true
}
}
} openclaw mcp add nvidia-elements --command npx --arg -y --arg @nvidia-elements/cli
mcp_servers:
nvidia-elements:
command: "npx"
args: ["-y", "@nvidia-elements/cli"] {
"McpServers": {
"nvidia-elements": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@nvidia-elements/cli"
]
}
}
} assistant mcp add nvidia-elements -t stdio -c npx -a -y @nvidia-elements/cli
{
"mcpServers": {
"nvidia-elements": {
"command": "npx",
"args": [
"-y",
"@nvidia-elements/cli"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.
- 19 Sept 26 −5
- CVE-2026-77301 affects this package: high ▼ security
- Known CVEs: partial → fail ▼ security
- CVE-2026-76845 no longer affects this package ▲ security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67.
- 15 Sept 26 −3
No change was recorded against any check on this day. Stability & Change Management went from 83 to 63.
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: 1667 → 1462 ▲ functional
- Schema quality: excellent → good functional
- Package version: 2.2.2 → 2.2.3 functional
- 9 Sept 26 +1
- CVE-2026-76845 affects this package ▼ security
- Known CVEs: pass → partial ▼ security
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 21 Sept 2026 · Analysed npm/@nvidia-elements/cli@2.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | NVIDIA/elements |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/NVIDIA/elements/.github/workflows/ci.yml@refs/heads/main |
| Rekor log index | 2800165778 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f0e09e8b9b52e2c89d59fa53e03d70c9c620077eb91c36c81bda016739f7be280c63d338a73e2151e3261bf889909d2003ca395cf843bcaab4a929a8e |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-7q85-xj36-vmfc | CVE-2026-77301 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vwc7-r8mq-g2x9 | CVE-2026-76845 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 288 packages
| Packages resolved | 288 |
|---|---|
| Stale | 93 |
| No linked repository | 2 |
| 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 →
api_get API Get ~130
Get documentation known components or attributes by name (nve-*). Limit: 3
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| names | array | yes | 1 to 3 component or attribute names (e.g., ["nve-button"] or ["nve-button", "nve-text"]). Tip: Use the list tool to get a summary list of all available components and attribute APIs. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
api_icons_list API Icons List ~75
Get list of all available icon names for nve-icon and nve-icon-button.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
api_imports_get API Imports Get ~33
Get esm imports for a given HTML template using Elements APIs (nve-*).
| Name | Type | Req | Description |
|---|---|---|---|
| template | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | array | – | – |
| status | string | – | – |
No examples provided.
api_list API List ~72
Get list of all available Elements (nve-*) APIs and components.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
api_tokens_list API Tokens List ~94
Get available semantic CSS custom properties / design tokens for theming.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| query | string | – | Optional search query used to filter tokens by name, value, or description before rendering. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
api_validate API Validate ~165
Check supported files or supplied HTML or JSON content with the recommended Elements lint rules.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Optional path for supplied content. Required for JSON content. |
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| lang | string | – | Content language when checking supplied content. |
| maxDiagnostics | number | – | Maximum number of diagnostics returned. Summary counts remain complete. |
| paths | array | – | HTML or JSON files and glob patterns relative to the current directory. |
| template | string | – | HTML or JSON content to check. Defaults to HTML; provide lang=json and filename for JSON. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
cli_upgrade CLI Upgrade ~41
Downloads and installs the latest version of the nve CLI. On macOS/Linux this runs the shell bootstrapper, on Windows it runs the PowerShell bootstrapper.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | object | – | – |
| status | string | – | – |
No examples provided.
examples_get Examples Get ~90
Get the full template of a known example or pattern by id.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| id | string | yes | The id of the example or pattern to get the full template of. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
examples_list Examples List ~86
Get a summary list of available Elements (nve-*) starter templates, patterns and example code snippets. Use this to browse all available examples.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
examples_render Examples Render ~112
Render an ad-hoc Elements (nve-*) HTML template in the MCP App preview iframe. The template is linted against Elements APIs before rendering. Lint failures return a tool error instead of rendering the template. Use this to preview compositions you author. Templates should be self-contained HTML — the iframe loads the Elements bundle and themes automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional human-readable label for the preview. |
| template | string | yes | HTML template to render. Should use Elements (nve-*) components. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | object | – | – |
| status | string | – | – |
No examples provided.
packages_changelogs_get Packages Changelogs Get ~93
Retrieve changelog details by package name.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Format of output. Use 'json' ONLY when you need to programmatically process the data. For reading/understanding, use the default 'markdown' format which is more readable and uses fewer tokens. |
| limit | number | – | Max number of versions to return. |
| name | string | yes | Available package changelogs. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | – | – | – |
| status | string | – | – |
No examples provided.
packages_get Packages Get ~25
Get details for a specific Elements package.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Available packages. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | string | – | – |
| status | string | – | – |
No examples provided.
packages_list Packages List ~17
Get latest published versions of all Elements packages.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | string | – | – |
| status | string | – | – |
No examples provided.
project_create Project Create ~133
Create a new starter project.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Provide the current working directory. |
| start | boolean | – | Run the starter project service/process after creation. This is will prevent the tool from exiting. |
| type | string | yes | The starter to create. `angular`| `bundles`| `eleventy`| `go`| `go-htmx`| `hugo`| `lit-library`| `mcp-app`| `nextjs`| `nuxt`| `react`| `solidjs`| `svelte`| `typescript`| `vue` |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | object | – | – |
| status | string | – | – |
No examples provided.
project_setup Project Setup ~61
Setup or update a project to use Elements. Configures MCP, adds core dependencies if missing, and updates packages to the latest versions. Use the packages_get tool to get package specific integration and installation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Provide the current working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | object | – | – |
| status | string | – | – |
No examples provided.
project_validate Project Validate ~49
Validate project setup and check for configuration issues, outdated dependencies, or missing required packages.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Provide the current working directory. |
| type | string | yes | Type of project to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| result | object | – | – |
| status | string | – | – |
No examples provided.
What is the NVIDIA Elements MCP server?
NVIDIA Elements is an MCP server listed in the public MCP registry as io.github.NVIDIA/elements. NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles. This page covers its npm package (@nvidia-elements/cli).
Is the NVIDIA Elements MCP server safe to use?
NVIDIA Elements scores 89 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 NVIDIA Elements MCP server expose?
NVIDIA Elements exposes 16 tools: api_list, api_get, api_validate, api_imports_get, api_tokens_list, and 11 more. Their descriptions and schemas cost roughly 1,276 tokens of context every time the server is loaded.
Is the NVIDIA Elements MCP server still maintained?
NVIDIA Elements is still listed as active in the MCP registry. We last reached this channel on 21 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 NVIDIA Elements MCP server under?
NVIDIA Elements declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.