NexArt MCP Server
io.github.artnames/nexart-mcp-serverartnamesstreamable-httpv0.2.0Scanned
Seven hosted verification/lookup tools; hosted certification disabled. Opt-in stdio recording.
7 tools: 5 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the NexArt MCP Server can do
The NexArt MCP Server is published by the GitHub account artnames. It has 7 tools. It can create or change data (5 tools: nexart_verify_ai_cer, nexart_verify_consequential_cer, nexart_verify_governed_execution, nexart_verify_project_bundle and 1 more), but cannot delete data. 2 tools only read.
3 tools bring in text other people can write (nexart_lookup_cer, nexart_lookup_project_bundle and nexart_verify_node_receipt).
The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 5Claude Code: ask
nexart_verify_ai_cerVerify inline AI CER V1/V2 integrity using the NexArt SDK.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
Description, as the server wrote it Verify inline AI CER V1/V2 integrity using the NexArt SDK. No signature, signer-trust or completeness claim.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nexart_verify_consequential_cerVerify inline consequential CER integrity.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
Description, as the server wrote it Verify inline consequential CER integrity. Producer identity and reported actions are not authenticated.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nexart_verify_governed_executionVerify inline governed execution 0.1/0.2 with explicit version dispatch.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
Description, as the server wrote it Verify inline governed execution 0.1/0.2 with explicit version dispatch. No state-hash or producer authentication.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
nexart_verify_node_receiptVerify a CER receipt Ed25519 signature with the published SDK.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Verify a CER receipt Ed25519 signature with the published SDK. Signature, binding, lifecycle and server-pinned trust are separate; Project receipts are unsupported.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
nexart_verify_project_bundleVerify an inline Project Bundle and embedded AI CERs using the SDK; require project hash integrity.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
Description, as the server wrote it Verify an inline Project Bundle and embedded AI CERs using the SDK; require project hash integrity.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
nexart_lookup_cerLook up one exact public NexArt hash.Reads text others writeNo findings
Why it is in this group
- The name "nexart_lookup_cer" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Look up one exact public NexArt hash. Return safe summaries and local returned-bundle integrity, not raw evidence or attestation authenticity.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
nexart_lookup_project_bundleLook up one exact public NexArt hash.Reads text others writeNo findings
Why it is in this group
- The name "nexart_lookup_project_bundle" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Look up one exact public NexArt hash. Return safe summaries and local returned-bundle integrity, not raw evidence or attestation authenticity.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:19 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.nexart.io/: tools/list returned 7 tools to an anonymous client, including nexart_verify_ai_cer (write), nexart_verify_consequential_cer (write), nexart_verify_governed_execution (write), nexart_verify_project_bundle (write), nexart_verify_node_receipt (write)
Findings
Matches of fixed checks, with the text they matched.
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
The input schema at properties.bundle.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bundle.description: "...inline NexArt artifact. No URLs, paths, credentials or openings."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http nexart https://mcp.nexart.io/claude mcp add --transport http nexart https://mcp.nexart.io/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nexart__nexart_lookup_cer",
"mcp__nexart__nexart_lookup_project_bundle"
],
"ask": [
"mcp__nexart__nexart_verify_ai_cer",
"mcp__nexart__nexart_verify_consequential_cer",
"mcp__nexart__nexart_verify_governed_execution",
"mcp__nexart__nexart_verify_project_bundle",
"mcp__nexart__nexart_verify_node_receipt"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nexart. Review it before you use it.
Capability tags behind 3 rules
- mcp__nexart__nexart_lookup_cer untrusted-input
- mcp__nexart__nexart_lookup_project_bundle untrusted-input
- mcp__nexart__nexart_verify_node_receipt untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.artnames/nexart-mcp-server/verify?hash=4a8237299e4627f2fc0d6cd35e551a2d5591b4a47f481b64e03baba6d57f46bc" | jq -e '.changed == false'Pinned hash 4a8237299e46, from Nov 17, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.artnames/nexart-mcp-server/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.artnames/nexart-mcp-server)Source: MCP Registry · repository. Synced Nov 17, 2026, 10:17 UTC.
NexArt MCP Server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NexArt MCP Server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the NexArt MCP Server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the NexArt MCP Server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the NexArt MCP Server have?
- 7 tools: 5 write, 2 read. nexart_verify_ai_cer, nexart_verify_consequential_cer, nexart_verify_governed_execution, nexart_verify_project_bundle, nexart_verify_node_receipt, nexart_lookup_cer and nexart_lookup_project_bundle.
Does the NexArt MCP Server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NexArt MCP Server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the NexArt MCP Server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.