AccordTrace
REMOTE · ACCORDTRACE.NOTARY-LABS.WORKERS.DEV · SCANNED SEP 28
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 382 tokens (~42/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management75
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 6 additions. See how to fix → Fail
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · accordtrace.notary-labs.workers.dev
claude mcp add --transport http kosta1985-accord-trace 'https://accordtrace.notary-labs.workers.dev/mcp'
{
"mcpServers": {
"kosta1985-accord-trace": {
"url": "https://accordtrace.notary-labs.workers.dev/mcp"
}
}
} {
"servers": {
"kosta1985-accord-trace": {
"type": "http",
"url": "https://accordtrace.notary-labs.workers.dev/mcp"
}
}
} [mcp_servers.kosta1985-accord-trace] url = "https://accordtrace.notary-labs.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kosta1985-accord-trace": {
"type": "remote",
"url": "https://accordtrace.notary-labs.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add kosta1985-accord-trace --url 'https://accordtrace.notary-labs.workers.dev/mcp' --transport streamable-http
mcp_servers:
kosta1985-accord-trace:
url: "https://accordtrace.notary-labs.workers.dev/mcp" {
"McpServers": {
"kosta1985-accord-trace": {
"Transport": "http",
"Url": "https://accordtrace.notary-labs.workers.dev/mcp"
}
}
} assistant mcp add kosta1985-accord-trace -t streamable-http -u 'https://accordtrace.notary-labs.workers.dev/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 72 to 75.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 65 to 68.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 58 to 62.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 48 to 52.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 42 to 45.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 35 to 38.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://accordtrace.notary-labs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=notary-labs.workers.dev | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | eb5e5097269076030e6ef26d9192deea |
| SANs: notary-labs.workers.dev, *.notary-labs.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of accordtrace.notary-labs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none'; frame-ancestors 'none'; base-uri 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://accordtrace.notary-labs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://accordtrace.notary-labs.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accord_trace_create_proof ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
| metadata | object|null | – | – |
No output schema declared.
No examples provided.
accord_trace_get_proof ~31
Retrieve public non-secret AccordTrace proof metadata by proof ID.
| Name | Type | Req | Description |
|---|---|---|---|
| proof_id | string | yes | – |
No output schema declared.
No examples provided.
accord_trace_hash ~30
Compute AccordTrace canonical SHA-256 for JSON-compatible data without creating a proof.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | – |
No output schema declared.
No examples provided.
accord_trace_network_capabilities ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
accord_trace_network_stats ~34
Read aggregate live affiliate-network states, distinguishing generated invitations, attributions, qualified direct sales, earned commissions and paid commissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
accord_trace_passport_product_capabilities ~35
Read the live Agent Passport Certificate product price and commercial readiness gates. Read-only; it never initiates checkout.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
accord_trace_resolve_referral ~44
Resolve a direct AccordTrace referral code to its active public referral record and disclosure without reserving attribution or creating a sale.
| Name | Type | Req | Description |
|---|---|---|---|
| referral_code | string | yes | – |
No output schema declared.
No examples provided.
accord_trace_verify ~52
Verify an AccordTrace recorded proof, optionally compare supplied data/hash, and verify an issuer signature when one is present.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
| hash | string | – | – |
| proof_id | string | yes | – |
No output schema declared.
No examples provided.
accord_trace_wallet_capabilities ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.