MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

NVIDIA Elements

Current Spec Verified Publisher unverified Confidence: Good (0.85)

NVIDIA Elements is an MCP server published by NVIDIA with verified support for the current MCP specification revision (2026-07-28). Last verified 2026-08-20.

Does NVIDIA Elements support the current MCP specification (2026-07-28)?

Yes. NVIDIA Elements has verified support for MCP revision 2026-07-28, the current stable specification (last verified 2026-08-20).

Is NVIDIA Elements a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for NVIDIA Elements (as of 2026-08-20).

How do I connect to NVIDIA Elements?

NVIDIA Elements is available via the package npm:@nvidia-elements/cli, the official MCP Registry under io.github.NVIDIA/elements, the source repository at https://github.com/nvidia/elements. Authentication: unknown. Transports: stdio.

Does NVIDIA Elements support MCP revision 2026-07-28?

Yes. NVIDIA Elements supports MCP revision 2026-07-28 (checked 2026-08-20).

When were NVIDIA Elements's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

NVIDIA Elements UI design system and agent tools for AI/ML, robotics, and autonomous vehicles.

Which MCP spec revisions does NVIDIA Elements support?

NVIDIA Elements has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2026-07-28 Supported Source

How widely adopted is NVIDIA Elements?

Ranked #398 in The MCP 500 with Adoption Index 47.56 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 159 API ·
GitHub stars 86 API ·
GitHub forks 16 API ·
Last push 2026-09-15T14:09:27Z API ·
Repository archived no API ·

Repository and package signals for NVIDIA Elements

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
6
Primary language
TypeScript
License (repository)
Apache-2.0
Continuous integration
Present
Tests
None detected
Security policy
Present

Declared topics: ai, angular, autonomous-vehicles, cli, design-system, design-tokens, generative-ai, mcp, mcp-server, react, robotics, theming, typescript, ui, ui-components, vue, web-component, web-components — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
2.1.10
Last published
First published
Releases
33
License (package)
Apache-2.0
Maintainers
2
Direct dependencies
14
Unpacked size
13.3 MB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.NVIDIA/elements at version 2.1.9 - lists package npm:@nvidia-elements/cli and repository https://github.com/nvidia/elements - accessed
  2. npm registry metadata for @nvidia-elements/cli at published version 2.1.10, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/server, which resolves to @modelcontextprotocol/server@2.0.0 - accessed
  3. Published artifact of @modelcontextprotocol/server@2.0.0, retrieved 2026-08-20 - the artifact declares revision 2026-07-28 and implements the stateless server/discover method. Read from the artifact itself, not from release notes - accessed