# AccordTrace (remote · accordtrace.notary-labs.workers.dev)

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

- Trust score: 67/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `accordtrace.notary-labs.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/kosta1985-accord-trace/accordtrace.md), [page](https://verifymcp.io/servers/kosta1985-accord-trace/accordtrace)

## Channel facts

- Endpoint: `https://accordtrace.notary-labs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 382 tokens (~42/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 75/100
  - Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the AccordTrace MCP server?

AccordTrace is a hosted endpoint at https://accordtrace.notary-labs.workers.dev/mcp, 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.

### Claude

```bash
claude mcp add --transport http kosta1985-accord-trace 'https://accordtrace.notary-labs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kosta1985-accord-trace": {
      "url": "https://accordtrace.notary-labs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kosta1985-accord-trace": {
      "type": "http",
      "url": "https://accordtrace.notary-labs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kosta1985-accord-trace]
url = "https://accordtrace.notary-labs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kosta1985-accord-trace": {
      "type": "remote",
      "url": "https://accordtrace.notary-labs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kosta1985-accord-trace --url 'https://accordtrace.notary-labs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kosta1985-accord-trace:
    url: "https://accordtrace.notary-labs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kosta1985-accord-trace": {
      "Transport": "http",
      "Url": "https://accordtrace.notary-labs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kosta1985-accord-trace -t streamable-http -u 'https://accordtrace.notary-labs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kosta1985-accord-trace": {
      "type": "http",
      "url": "https://accordtrace.notary-labs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 72 to 75.

### 2026-09-22 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 65 to 68.

### 2026-09-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 58 to 62.

### 2026-09-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 48 to 52.

### 2026-09-15 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 42 to 45.

### 2026-09-13 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 35 to 38.

## MCP tools (9)

### `accord_trace_create_proof` (~56 tokens)

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.

Input parameters:

- `data` (required)
- `metadata` (object|null)

### `accord_trace_verify` (~52 tokens)

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

Input parameters:

- `data`
- `hash` (string)
- `proof_id` (string, required)

### `accord_trace_get_proof` (~31 tokens)

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

Input parameters:

- `proof_id` (string, required)

### `accord_trace_hash` (~30 tokens)

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

Input parameters:

- `data` (required)

### `accord_trace_network_capabilities` (~46 tokens)

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.

### `accord_trace_network_stats` (~34 tokens)

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

### `accord_trace_passport_product_capabilities` (~35 tokens)

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

### `accord_trace_wallet_capabilities` (~54 tokens)

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.

### `accord_trace_resolve_referral` (~44 tokens)

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

Input parameters:

- `referral_code` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kosta1985-accord-trace/accordtrace#diagnostics

## Score history

- 2026-09-28: 67
- 2026-09-27: 67
- 2026-09-26: 67
- 2026-09-25: 67
- 2026-09-24: 67
- 2026-09-23: 66
- 2026-09-22: 66
- 2026-09-21: 65
- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 64
- 2026-09-17: 64
- 2026-09-16: 63
- 2026-09-15: 63
- 2026-09-14: 62
- 2026-09-13: 62
- 2026-09-12: 61
- 2026-09-11: 61
- 2026-09-10: 60
- 2026-09-09: 60
- 2026-09-08: 59
- 2026-09-07: 59
- 2026-09-06: 58
- 2026-09-05: 58
- 2026-09-04: 72
- 2026-09-03: 72
- 2026-09-02: 72
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 70

## Common questions

### What is the AccordTrace MCP server?

AccordTrace is an MCP server listed in the public MCP registry as io.github.Kosta1985/accord-trace. Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST. This page covers its hosted endpoint (https://accordtrace.notary-labs.workers.dev/mcp).

### Is the AccordTrace MCP server safe to use?

AccordTrace scores 67 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 AccordTrace MCP server expose?

AccordTrace exposes 9 tools: accord_trace_create_proof, accord_trace_verify, accord_trace_get_proof, accord_trace_hash, accord_trace_network_capabilities, and 4 more. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.

### Does the AccordTrace MCP server require authentication?

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

### Is the AccordTrace MCP server still maintained?

AccordTrace is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://accordtrace.notary-labs.workers.dev/mcp
- Repository: https://github.com/Kosta1985/notary-protocol
- Website: https://accordtrace.notary-labs.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/kosta1985-accord-trace/accordtrace.xml
- Changelog JSON feed: https://verifymcp.io/servers/kosta1985-accord-trace/accordtrace.json
- HTML version of this page: https://verifymcp.io/servers/kosta1985-accord-trace/accordtrace