AccordTrace

io.github.Kosta1985Published by GitHub account Kosta1985v0.2.1Updated Oct 24, 2026

Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

AccordTrace is a remote MCP service for creating and verifying tamper-evident hash-bound proofs and reading agent passport, wallet and referral policy data.

What you can do
Create hash-bound service records, optionally with an Ed25519 issuer signature, without storing the submitted content, and compute canonical SHA-256 hashes of JSON data without creating a proof. Verify a recorded proof, optionally comparing supplied data or hash and checking an issuer signature, and retrieve public non-secret proof metadata by proof ID. Read live policy and status for the one-level agent affiliate network, including economics, anti-downline rules, payout activation and aggregate invitation, attribution, sales and commission states. Read product price and readiness gates for the Agent Passport Certificate, and read wallet feature gates, signing contract, balance policy and no
When to use it
Use it when an agent needs an independent, verifiable receipt for a handoff, approval, workflow checkpoint or generated artifact, or when it receives a proof ID from another agent and must check it. Also useful for reading machine-readable passport, wallet and referral policy before deciding whether to engage.
Requirements
Remote Streamable HTTP endpoint; no Authorization header is currently required for the public evidence and discovery surface. No account, card or model API key is needed for the REST starter. The optional local handoff example needs Node.js 22+ and a repository clone.
Before you install
Proofs attest integrity and service-recorded time only, not truth, authorship, legality or identity. Submitted content is not stored, but proofs are public, so use synthetic or non-sensitive data. Paid certificates cost US$2 and referral commissions are one-level; checkout and cash payouts are described as disabled or fail-closed. Wallet tools are read-only and never move funds.

Installation

In SourceWeft

  1. Open AccordTrace in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Kosta1985%2Faccord-trace/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "accordtrace": {
      "type": "http",
      "url": "https://accordtrace.notary-labs.workers.dev/mcp"
    }
  }
}

README

AccordTrace

Cryptographic receipts, portable Agent Passports, and verifiable infrastructure for AI agents.

Start here: Founding 1000

The first 1,000 eligible active cryptographic Agent Passports can claim one AccordTrace-signed Agent Passport Certificate for US$0. No card. One grant per Passport key. Free Founding grants create no paid sale, no revenue event, and no direct-referral commission.

Check live availability · Open Founding 1000 · Read agent instructions

A Founding Certificate is a portable AccordTrace-signed issuance artifact bound to the active Passport public-key fingerprint and marked with a Founding ordinal. It proves AccordTrace issuance bound to cryptographic key control. It does not prove legal identity, KYC, safety, Trust, validation, ownership, investment value, or that one Passport key equals one unique human or company.

Machine claim flow

  1. Create or maintain an active cryptographic Agent Passport with POST /api/v1/security/passports.
  2. Check GET /api/v1/passport-product/founding-1000 for live availability.
  3. Sign the canonical Founding claim with the active Passport Ed25519 key using domain accordtrace.passport-product.founding-1000.claim.v1.
  4. Submit the signed request to POST /api/v1/passport-product/founding-1000/claim.
  5. Retain the returned signed Certificate and Founding ordinal.

Private keys stay with the agent. The Founding claim is idempotent and the campaign is hard-capped at 1,000 durable slots.

Standard Certificate economics

Outside the free cohort, the standard Agent Passport Certificate policy is US$2 one time, subject to commercial readiness gates.

The paid referral model is deliberately one-level:

text
Agent A direct referral -> Agent B genuine qualifying US$2 Certificate purchase -> Agent A US$1 qualifying commission

There are no downline commissions. Founding 1000 free grants are outside the paid referral path and create US$0 referral commission. Referral activity never improves Trust, validation, identity, or security status.

Cash affiliate payout execution remains disabled until payout-provider, KYC/tax, and final affiliate-terms gates are activated. Commercial checkout remains fail-closed unless Stripe, signing, activation, and end-to-end payment-readiness requirements are satisfied. A browser redirect is never payment truth.

Free evidence interoperability test

Pass the proof. Not just the claim. Create synthetic evidence, verify the original, change one field, and require rejection. No account, card, or model API key is needed for the REST starter.

Run the handoff test · Read the source · Share a result

bash
node examples/agent-handoff/campaign.mjs --source github

Requires Node.js 22+ and a clone of this repository. Running it creates one synthetic public proof and verifies it twice. A one-client test is not an independent two-agent integration report. Use synthetic/non-sensitive data only.

Core public agent infrastructure

AccordTrace is agent-first infrastructure for AI-agent identity key control, handoffs, artifact provenance, approvals, audit trails, verification, capability policy, continuity monitoring, and economic evidence. Another agent can inspect or verify records later through REST, MCP, A2A, or OpenAPI.

Use AccordTrace when an agent needs to answer questions like:

  • Did the artifact I received match what the previous agent actually handed off?
  • Can I retain an independent receipt for an approval or workflow checkpoint?
  • Can another agent verify this result without trusting my local storage?
  • Can I attach portable provenance to a deployment, report, tool result, or generated artifact?
  • Can I present a key-bound Agent Passport without sending my private key?
  • Can I inspect Wallet, referral, security, validation, or capability policy in machine-readable form?

Public discovery:

Repository guides:

Connect an agent in 60 seconds

For any client that supports remote Streamable HTTP MCP, add:

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

Then let the agent use AccordTrace before important handoffs or when it receives a proof ID from another agent. Full copy-paste integration examples for OpenAI Agents SDK, JavaScript/TypeScript, generic MCP, A2A, OpenAPI, and REST are in Connect your agent.

Cline remote MCP

json
{  "mcpServers": {    "accordtrace": {      "type": "streamableHttp",      "url": "https://accordtrace.notary-labs.workers.dev/mcp",      "disabled": false,      "autoApprove": []    }  }}

The current public evidence/discovery surface does not require an Authorization header. See llms-install.md for UI steps, a read-only connection check, a synthetic proof test, and safety boundaries.

Try the 15-minute agent handoff challenge

Create a proof in one client, pass the proof ID and synthetic evidence to a different agent, and verify the handoff through REST, MCP, or A2A. Runnable examples cover generic clients, OpenAI remote MCP, and the Claude MCP connector.

Run the interoperability challenge · Browse the handoff examples · Public interoperability board

For agent framework and registry maintainers

AccordTrace is callable infrastructure, not a closed dashboard. Frameworks, MCP/A2A directories, agent templates, workflow libraries, and developer communities can point agents directly at the public endpoints above or use the distribution kit.

Suggested neutral description:

AccordTrace provides cryptographic Agent Passports, tamper-evident evidence, verification, least-privilege capability policy, continuity monitoring, and machine-readable economic infrastructure for AI agents. During Founding 1000, the first 1,000 eligible active Passport keys can claim one signed Agent Passport Certificate for US$0; free grants create no referral commission.

External agents can create and verify tamper-evident records anonymously for synthetic interoperability tests. AccordTrace attests integrity and service-recorded time. It does not establish truth, authorship, legality, fairness, delivery, payment, legal identity, or commercial quality by itself.

Start with REST

Create a proof:

bash
curl -X POST https://accordtrace.notary-labs.workers.dev/api/v1/proofs \  -H 'content-type: application/json' \  -d '{"data":{"event":"agent.handoff","artifact":"synthetic-demo"},"metadata":{"synthetic":true}}'

Then verify the returned proof ID with the exact same evidence through the verification endpoint or another supported agent interface.

Agent-facing discovery terms

AccordTrace is designed for agent evidence, AI audit trails, MCP verification, A2A verification, multi-agent handoffs, cryptographic agent receipts, workflow provenance, autonomous-agent approvals, tamper-evident AI logs, agent accountability, verifiable agent actions, AI Agent Passports, portable agent identity certificates, Agent Wallet policy discovery, and direct agent-to-agent referral discovery.

See the repository documentation for protocol details, SDKs, threat boundaries, launch economics, campaign controls, and deployment information.

Source: README.md at commit ecca5e3

Tools

9

accord_trace_create_proof

Create an AccordTrace hash-bound service record. If issuer signing is configured, the proof also carries an Ed25519 issuer signature. Submitted content is not stored.

Parametersdatarequiredmetadata

accord_trace_verify

Verify an AccordTrace recorded proof, optionally compare supplied data/hash, and verify an issuer signature when one is present.

Parametersdatahashproof_idrequired

accord_trace_get_proof

Retrieve public non-secret AccordTrace proof metadata by proof ID.

Parametersproof_idrequired

accord_trace_hash

Compute AccordTrace canonical SHA-256 for JSON-compatible data without creating a proof.

Parametersdatarequired

accord_trace_network_capabilities

Read the live one-level AccordTrace Agent Affiliate Network policy, economics, anti-downline rules and payout activation status. Read-only; it does not enroll or attribute an agent.

Takes no parameters.

accord_trace_network_stats

Read aggregate live affiliate-network states, distinguishing generated invitations, attributions, qualified direct sales, earned commissions and paid commissions.

Takes no parameters.

accord_trace_passport_product_capabilities

Read the live Agent Passport Certificate product price and commercial readiness gates. Read-only; it never initiates checkout.

Takes no parameters.

accord_trace_wallet_capabilities

Read machine-facing Agent Wallet feature gates, Ed25519 signing contract, funded-balance policy, USDC representation and explicit no-credit/no-lending boundary. Read-only; it never creates a wallet or moves funds.

Takes no parameters.

accord_trace_resolve_referral

Resolve a direct AccordTrace referral code to its active public referral record and disclosure without reserving attribution or creating a sale.

Parametersreferral_coderequired

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts