Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NexArt MCP Server

NPM · @NEXART/MCP-SERVER · 2 COMPONENTS

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

+3 this week 65 Trust /100

Last scanned (22 hours ago)

Scores higher than 37% of npm servers

Category Security

Trust breakdown (7 categories)

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
  • 3 of 6 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability63
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 375 tokens (~53/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% 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 7 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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

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 →

Changelog

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.

  • 21 Nov 26 +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.

  • 18 Nov 26 +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.

  • 17 Nov 26 0
    • Package version: 0.1.0 → 0.2.0 functional
  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 13 Nov 26 61

    First indexed and scored.

Diagnostics

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 Nov 2026 · Analysed npm/@nexart/mcp-server@0.2.0

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 6 packages
Packages resolved 6
No linked repository 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~375 tokens

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 →

Tool Tokens
nexart_lookup_cer ~46

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

NameTypeReqDescription
certificateHashstringyes–
NameTypeReqDescription
contractVersionstringyes–
family–yes–
integritystringyes–
integrityScopestringyes–
limitationsarrayyes–
lookupstringyes–
nodeSignaturestringyes–
reasonCodestringyes–
receiptPresentbooleanyes–
sdk–yes–
signerTruststringyes–

No examples provided.

nexart_lookup_project_bundle ~46

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

NameTypeReqDescription
projectHashstringyes–
NameTypeReqDescription
contractVersionstringyes–
family–yes–
integritystringyes–
integrityScopestringyes–
limitationsarrayyes–
lookupstringyes–
nodeSignaturestringyes–
reasonCodestringyes–
receiptPresentbooleanyes–
sdk–yes–
signerTruststringyes–

No examples provided.

nexart_verify_ai_cer ~56

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

NameTypeReqDescription
bundle–yesAn inline NexArt artifact. No URLs, paths, credentials or openings.
NameTypeReqDescription
artifactIntegritystringyes–
checksobjectyes–
contractVersionstringyes–
family–yes–
limitationsarrayyes–
protocol–yes–
reasonCodestringyes–
recordVersion–yes–
sdk–yes–
toolstringyes–

No examples provided.

nexart_verify_consequential_cer ~48

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

NameTypeReqDescription
bundle–yesAn inline NexArt artifact. No URLs, paths, credentials or openings.
NameTypeReqDescription
artifactIntegritystringyes–
checksobjectyes–
contractVersionstringyes–
family–yes–
limitationsarrayyes–
protocol–yes–
reasonCodestringyes–
recordVersion–yes–
sdk–yes–
toolstringyes–

No examples provided.

nexart_verify_governed_execution ~57

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

NameTypeReqDescription
bundle–yesAn inline NexArt artifact. No URLs, paths, credentials or openings.
NameTypeReqDescription
artifactIntegritystringyes–
checksobjectyes–
contractVersionstringyes–
family–yes–
limitationsarrayyes–
protocol–yes–
reasonCodestringyes–
recordVersion–yes–
sdk–yes–
toolstringyes–

No examples provided.

nexart_verify_node_receipt ~73

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

NameTypeReqDescription
certificateHashstringyes–
receipt–––
signatureB64Urlstring––
sourcestringyes–
NameTypeReqDescription
artifactIntegritystringyes–
contractVersionstringyes–
hashBindingstringyes–
keyLifecyclestringyes–
keyStatusstringyes–
lifecycleCodestringyes–
limitationsarrayyes–
nodeIdentitystringyes–
reasonCodestringyes–
sdk–yes–
signaturestringyes–
signerTruststringyes–

No examples provided.

nexart_verify_project_bundle ~49

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

NameTypeReqDescription
bundle–yesAn inline NexArt artifact. No URLs, paths, credentials or openings.
NameTypeReqDescription
artifactIntegritystringyes–
checksobjectyes–
contractVersionstringyes–
family–yes–
limitationsarrayyes–
protocol–yes–
reasonCodestringyes–
recordVersion–yes–
sdk–yes–
toolstringyes–

No examples provided.

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.

npm · @nexart/mcp-server

# add to Claude Code
claude mcp add artnames-nexart-mcp-server -- npx -y @nexart/mcp-server
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.