Verifiable AI Execution Through MCP
Certify AI agent executions with NexArt MCP.
NexArt MCP connects MCP-compatible AI agents and applications to NexArt. Agents can verify NexArt evidence, and, with your explicit authorisation, record execution evidence as Certified Execution Records, obtain NexArt Node certification and leave a record anyone can verify independently.
MCP does not record anything on its own. A record exists only when the agent or application actually calls the recording tool with the execution data it supplies. NexArt proves the integrity of what was submitted; it does not independently determine whether the agent's actions were correct or complete.
Get Started opens the MCP Integration page in your dashboard. You will be asked to sign in first if needed. The documentation is the package guide on npm.
How it works
- Use a NexArt account. Sign in with an existing NexArt account or create one. There is no separate MCP account.
- Configure an MCP credential. In the dashboard, select or create the NexArt API key the MCP server will use.
- Authorise automatic certification. Approve a certification policy for that key: visibility, permitted metadata, recovery recipient and expiry. A key alone never enables submission.
- Connect a supported AI platform. Add the NexArt MCP server to an MCP client that can launch a local stdio server.
- Submit execution evidence. The agent or application calls the recording tool with eligible execution evidence. Nothing is recorded unless the tool is invoked.
- Receive a verifiable record. NexArt returns a Certified Execution Record and a signed Node attestation that can be verified independently.
Execution evidence is not logging
Application logs, observability traces and governance dashboards describe activity inside the system that produced it, and that system can change them. A Certified Execution Record is sealed evidence: anyone holding it can check that it has not changed since it was created and, if certified, that a NexArt Node attested to it. It complements logging rather than replacing it.
Key capabilities
AI execution certification
Turn agent-supplied execution evidence into Certified Execution Records and, where authorised, NexArt Node certification.
Independent CER verification
Verification tools check record integrity locally, without trusting the system that produced the record.
Confidential execution commitments
Confidential records carry cryptographic commitments instead of plaintext, with recovery material encrypted to your public recipient.
Signed Node attestations
Receipts are signed by the NexArt Node and bound to the record hash. Signer trust is checked as a separate step.
Customer-controlled authorisation
Certification runs only under a policy you approve in the dashboard, and you can disable or revoke it.
Existing certification quotas
Certifications use your existing NexArt account and plan allowances. No separate MCP billing.
MCP-compatible integrations
Works through the Model Context Protocol with clients that support local stdio servers.
Integration methods
Available
Local MCP server
Package @nexart/mcp-server version 0.1.0, listed in the official MCP Registry as io.github.artnames/nexart-mcp-server. It runs over stdio on your machine and supports local verification tools and customer-authorised execution recording.
{
"mcpServers": {
"nexart": {
"command": "npx",
"args": ["--yes", "--package=@nexart/mcp-server@0.1.0", "nexart-mcp-server"]
}
}
}Read-only tools available without credentials:
- nexart_verify_ai_cer
- nexart_verify_consequential_cer
- nexart_verify_governed_execution
- nexart_verify_project_bundle
- nexart_lookup_cer
- nexart_lookup_project_bundle
- nexart_verify_node_receipt
Coming soon
Hosted MCP server
Endpoint https://mcp.nexart.io, Streamable HTTP transport. The hosted service is being integrated with the NexArt dashboard for credential management and automatic certification. It is not yet open for connections; use the local server today.
Confidentiality and security
- Confidential CERs store cryptographic commitments to inputs and outputs rather than the plaintext itself.
- Where supported, complete recovery material is encrypted to a public recipient you approve. NexArt never needs your private key.
- Any MCP server that processes your request, local or hosted, can see the execution data submitted to it while it is processed. Confidential records limit what is stored and published, not what the processing host receives.
- A valid signature shows that a record was signed by a specific key and has not changed since. Whether that signer is trusted is a separate check against published key information.
Developer resources
- NexArt MCP package on npm
- Official MCP Registry entry
- NexArt documentation
- Certified Execution Records
- NexArt Node
- Independent verifier at verify.nexart.io
- Dashboard MCP Integration page
- Independent verification · Confidential execution · AI agent execution
Frequently asked questions
How do I install the NexArt MCP server?
Install @nexart/mcp-server 0.1.0 from npm, or add it to an MCP client configuration using npx. It requires Node.js 24 and a client that can launch a local stdio MCP server.
Which tools does it provide?
Seven read-only verification and lookup tools work without credentials, including CER, Project Bundle and Node receipt verification. An opt-in recording tool creates confidential execution evidence and can request Node certification under an approved policy.
Does installing MCP certify every agent execution automatically?
No. A record is created only when the agent or application calls the recording tool with the execution data it supplies. NexArt does not observe client activity on its own.
How is certification authorised?
You approve a certification policy for a specific API key in the NexArt dashboard. A key without an approved policy cannot submit certifications, and policies can be disabled or revoked.
How do I verify a record?
Use the MCP verification tools, the NexArt SDK or the public verifier at verify.nexart.io. Verification checks integrity and Node attestation without relying on the system that produced the record.
Can the MCP server see my execution data?
Yes, while processing a request. Confidential records store commitments and encrypted recovery material rather than plaintext, but the server handling the request receives the data you submit.
How is MCP usage billed?
Certifications made through MCP count against your existing NexArt plan and certification allowance. There is no separate MCP plan.
Is a hosted MCP server available?
Not yet. A hosted server at mcp.nexart.io is being integrated with the NexArt dashboard and is not open for connections. Use the local npm package today.