NVIDIA Elements
NPM · @NVIDIA-ELEMENTS/CLI
NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.
Available components
Last scanned (20 hours ago)
Scores higher than 94% of npm servers
Category Developer Tools
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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via eslint > minimatch. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 96 of 302 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 2 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 1479 tokens (~77/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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% 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
Checks we ran (17)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −4
- Stability: pass → 0.73 functional
- 3 Nov 26 +3
- CVE-2023-54404 no longer affects this package ▲ security
- CVE-2026-111768 no longer affects this package ▲ security
- CVE-2026-111771 no longer affects this package ▲ security
- CVE-2026-111770 no longer affects this package ▲ security
- Known CVEs: CVE check failed: a known medium-severity CVE affects minimatch 10.2.6, reached via eslint > minimatch. A fixed version is available. security
- Package version: 2.2.15 → 2.2.16 functional
- 31 Oct 26 +15
- CVE-2026-118764 affects this package: high ▼ security
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 2.2.14 → 2.2.15 functional
- 29 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 2.2.13 → 2.2.14 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- CVE-2023-54404 affects this package: high ▼ security
- Malware scan: pass → unverified ▼ security
- Package version: 2.2.12 → 2.2.13 functional
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ 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 5 Nov 2026 · Analysed npm/@nvidia-elements/cli@2.2.16
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 | 3652194660 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d4cdb24a7b4a3c76fc2e5236928f1a0410ea7e6aa050ee3bad4df919bed9c2b0acb6aecbc3f094b4ebb05bd0378922af1f24b0a2455d881d2e6564b10 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 302 packages
| Packages resolved | 302 |
|---|---|
| Stale | 94 |
| 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 ~177
Check supported files or supplied HTML or JSON content with the recommended Elements lint rules.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Provide the current working directory. |
| 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 ~138
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`| `sphinx`| `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.
How do I install the NVIDIA Elements MCP server?
NVIDIA Elements runs locally as an npm package, launched with npx -y @nvidia-elements/cli mcp. 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 mcp
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 91 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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,293 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 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 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.
What did VerifyMCP test on the NVIDIA Elements MCP server?
VerifyMCP ran 17 checks on NVIDIA Elements, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.