# NexArt MCP Server (npm · @nexart/mcp-server)

Seven hosted verification/lookup tools; hosted certification disabled. Opt-in stdio recording.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.nexart.io`: 72/100, [markdown](https://verifymcp.io/servers/artnames-nexart-mcp-server/mcp.md), [page](https://verifymcp.io/servers/artnames-nexart-mcp-server/mcp)
- npm · `@nexart/mcp-server`: 65/100 (this document), [markdown](https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server.md), [page](https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@nexart/mcp-server`
- Version: `0.2.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-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 3 of 6 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 375 tokens (~53/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 40% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the NexArt MCP Server server?

NexArt MCP Server runs locally as an npm package, launched with npx -y @nexart/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add artnames-nexart-mcp-server -- npx -y @nexart/mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "artnames-nexart-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@nexart/mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "artnames-nexart-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@nexart/mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add artnames-nexart-mcp-server -- npx -y @nexart/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "artnames-nexart-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@nexart/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add artnames-nexart-mcp-server --command npx --arg -y --arg @nexart/mcp-server
```

### Hermes

```yaml
mcp_servers:
  artnames-nexart-mcp-server:
    command: "npx"
    args: ["-y", "@nexart/mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "artnames-nexart-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@nexart/mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add artnames-nexart-mcp-server -t stdio -c npx -a -y @nexart/mcp-server
```

### Other

```json
{
  "mcpServers": {
    "artnames-nexart-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@nexart/mcp-server"
      ]
    }
  }
}
```

## 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-21 (score 65, +1)

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

### 2026-11-18 (score 64, +1)

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

### 2026-11-17 (score 63, 0)

- [functional] Package version: 0.1.0 → 0.2.0

### 2026-11-16 (score 63, +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-14 (score 62, +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-13 (score 61)

First indexed and scored.

## MCP tools (7)

### `nexart_verify_ai_cer` (~56 tokens)

Verify inline AI CER V1/V2 integrity using the NexArt SDK. No signature, signer-trust or completeness claim.

Input parameters:

- `bundle` (required): An inline NexArt artifact. No URLs, paths, credentials or openings.

Output parameters:

- `artifactIntegrity` (string)
- `checks` (object)
- `contractVersion` (string)
- `family`
- `limitations` (array)
- `protocol`
- `reasonCode` (string)
- `recordVersion`
- `sdk`
- `tool` (string)

### `nexart_verify_consequential_cer` (~48 tokens)

Verify inline consequential CER integrity. Producer identity and reported actions are not authenticated.

Input parameters:

- `bundle` (required): An inline NexArt artifact. No URLs, paths, credentials or openings.

Output parameters:

- `artifactIntegrity` (string)
- `checks` (object)
- `contractVersion` (string)
- `family`
- `limitations` (array)
- `protocol`
- `reasonCode` (string)
- `recordVersion`
- `sdk`
- `tool` (string)

### `nexart_verify_governed_execution` (~57 tokens)

Verify inline governed execution 0.1/0.2 with explicit version dispatch. No state-hash or producer authentication.

Input parameters:

- `bundle` (required): An inline NexArt artifact. No URLs, paths, credentials or openings.

Output parameters:

- `artifactIntegrity` (string)
- `checks` (object)
- `contractVersion` (string)
- `family`
- `limitations` (array)
- `protocol`
- `reasonCode` (string)
- `recordVersion`
- `sdk`
- `tool` (string)

### `nexart_verify_project_bundle` (~49 tokens)

Verify an inline Project Bundle and embedded AI CERs using the SDK; require project hash integrity.

Input parameters:

- `bundle` (required): An inline NexArt artifact. No URLs, paths, credentials or openings.

Output parameters:

- `artifactIntegrity` (string)
- `checks` (object)
- `contractVersion` (string)
- `family`
- `limitations` (array)
- `protocol`
- `reasonCode` (string)
- `recordVersion`
- `sdk`
- `tool` (string)

### `nexart_lookup_cer` (~46 tokens)

Look up one exact public NexArt hash. Return safe summaries and local returned-bundle integrity, not raw evidence or attestation authenticity.

Input parameters:

- `certificateHash` (string, required)

Output parameters:

- `contractVersion` (string)
- `family`
- `integrity` (string)
- `integrityScope` (string)
- `limitations` (array)
- `lookup` (string)
- `nodeSignature` (string)
- `reasonCode` (string)
- `receiptPresent` (boolean)
- `sdk`
- `signerTrust` (string)

### `nexart_lookup_project_bundle` (~46 tokens)

Look up one exact public NexArt hash. Return safe summaries and local returned-bundle integrity, not raw evidence or attestation authenticity.

Input parameters:

- `projectHash` (string, required)

Output parameters:

- `contractVersion` (string)
- `family`
- `integrity` (string)
- `integrityScope` (string)
- `limitations` (array)
- `lookup` (string)
- `nodeSignature` (string)
- `reasonCode` (string)
- `receiptPresent` (boolean)
- `sdk`
- `signerTrust` (string)

### `nexart_verify_node_receipt` (~73 tokens)

Verify a CER receipt Ed25519 signature with the published SDK. Signature, binding, lifecycle and server-pinned trust are separate; Project receipts are unsupported.

Input parameters:

- `certificateHash` (string, required)
- `receipt`
- `signatureB64Url` (string)
- `source` (string, required)

Output parameters:

- `artifactIntegrity` (string)
- `contractVersion` (string)
- `hashBinding` (string)
- `keyLifecycle` (string)
- `keyStatus` (string)
- `lifecycleCode` (string)
- `limitations` (array)
- `nodeIdentity` (string)
- `reasonCode` (string)
- `sdk`
- `signature` (string)
- `signerTrust` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 64
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 61

## Common questions

### What is the NexArt MCP Server server?

NexArt MCP Server is listed in the public MCP registry as io.github.artnames/nexart-mcp-server. Seven hosted verification/lookup tools; hosted certification disabled. Opt-in stdio recording. This page covers its npm package (@nexart/mcp-server).

### Is the NexArt MCP Server server safe to use?

NexArt MCP Server scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 NexArt MCP Server server expose?

NexArt MCP Server exposes 7 tools: nexart_verify_ai_cer, nexart_verify_consequential_cer, nexart_verify_governed_execution, nexart_verify_project_bundle, nexart_lookup_cer, and 2 more. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.

### Is the NexArt MCP Server server still maintained?

NexArt MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 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 NexArt MCP Server server under?

NexArt MCP Server 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 NexArt MCP Server server?

VerifyMCP ran 15 checks on NexArt MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about NexArt MCP Server: Security disclosure. 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.

## Links

- npm package: https://www.npmjs.com/package/@nexart/mcp-server
- Socket report: https://socket.dev/npm/package/@nexart/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/artnames-nexart-mcp-server/nexart-mcp-server
