Accord Trace

What Accord Trace MCP server does

The Accord Trace MCP server exposes AccordTrace’s public agent infrastructure through Model Context Protocol. Its documented use cases include recording and verifying evidence, preserving artifact provenance, supporting agent handoffs, retaining approval or workflow receipts, and presenting key-bound Agent Passports without exposing private keys.

AccordTrace records can be inspected later through REST, MCP, A2A, or OpenAPI interfaces. The service is intended for agents that need an independently retrievable proof or receipt rather than relying only on local storage. It also publishes machine-readable surfaces for capability policy, security, validation, Wallet information, referrals, and related discovery data.

The Accord Trace MCP server is available at https://accordtrace.notary-labs.workers.dev/mcp. The repository identifies the service in the official MCP Registry as io.github.Kosta1985/accord-trace.

How it works

Agents connect to the remote Streamable HTTP MCP endpoint and use AccordTrace during important handoffs or when another agent supplies a proof ID. A typical workflow creates evidence, passes the proof identifier and synthetic evidence to another agent, and verifies that the received data matches the original. The repository also describes a negative test: changing one field should cause verification to reject the modified evidence.

Agent Passports use cryptographic key control. Private keys remain with the agent, while a Passport public-key fingerprint can bind an issuance or certificate to that key. AccordTrace records integrity and service-recorded time; those records do not independently establish truth, authorship, legality, payment, delivery, fairness, or commercial quality.

For a local starter test, the repository provides a Node.js campaign script. It requires Node.js 22 or later and a repository clone, creates synthetic public proof, and verifies it twice. The documented test is not an independent two-agent integration report.

Setup and configuration

Add the remote endpoint to an MCP client that supports Streamable HTTP:

https://accordtrace.notary-labs.workers.dev/mcp

The README provides a Cline configuration using type: "streamableHttp", the endpoint URL, and an empty autoApprove list. The current public evidence and discovery surface does not require an Authorization header. Repository installation guidance is available in llms-install.md, while connection examples cover generic MCP, JavaScript or TypeScript, OpenAI Agents SDK, A2A, OpenAPI, and REST.

No required environment variables or local service process are documented for connecting to the public endpoint.

Tools and capabilities

Documented capabilities include:

• Creating and verifying tamper-evident evidence.
• Supporting artifact provenance and cross-agent handoffs.
• Retaining receipts for approvals and workflow checkpoints.
• Presenting cryptographic Agent Passports without sending private keys.
• Inspecting capability policy, security, validation, Wallet, and economic information.
• Exposing the same service through MCP alongside REST, A2A, and OpenAPI.

Limitations and notes

Use synthetic or non-sensitive data for the public interoperability tests. A successful proof confirms record integrity and service-recorded time, not the truth of the underlying claim. One client running the handoff script does not demonstrate an independent two-agent integration.

The Founding Certificate is bound to an active Passport public-key fingerprint and an ordinal. It does not prove legal identity, KYC, safety, trust, ownership, investment value, or that one key represents one unique person or company. Commercial checkout and affiliate payout features have separate readiness and activation conditions; they are not required for the public evidence test.