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

REMOTE · MCP.NEXART.IO · 2 COMPONENTS

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

72 Trust /100

Last scanned (19 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
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 Management13
  • Stability observed for 4 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 (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

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

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.1.0 → 0.2.0 functional
  • 17 Nov 26 70

    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 · Probed https://mcp.nexart.io/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.nexart.io CN=YE2,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 5ec2a59ea1b402bb5ca34dcac06960aeb20
SANs: mcp.nexart.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.nexart.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
nexart.io. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nexart.io/ Verified 200
http (plaintext) http://mcp.nexart.io/ HTTPS enforced 301 https://mcp.nexart.io:443/
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 is a hosted endpoint at https://mcp.nexart.io/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.nexart.io

# add to Claude Code
claude mcp add --transport http artnames-nexart-mcp-server 'https://mcp.nexart.io/'
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 hosted endpoint (https://mcp.nexart.io/).

Is the NexArt MCP Server server safe to use?

NexArt MCP Server scores 72 out of 100 on VerifyMCP. 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.

Does the NexArt MCP Server server require authentication?

No. We connected to NexArt MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the NexArt MCP Server server?

VerifyMCP ran 13 checks on NexArt MCP Server, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.