Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tracea

REMOTE · MCP.TRACEA.ONLINE

Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.

0 this week 80 Trust /100

Last scanned (22 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 2307 tokens (~100/item across 23 items; 23 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 19 Oct 26 0
    • Schema quality: 84 → 100 ▼ functional
    • New tool “get_verification_card” functional
    • New tool “tracea_anchor_demarche” functional
    • New tool “tracea_check_demarche” functional
    • New tool “tracea_demarche_document” functional
    • New tool “tracea_demarche_preuve” functional
    • New tool “tracea_demarche_schema” functional
    • New tool “tracea_list_demarches” functional
    • New tool “tracea_signature” functional
  • 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
  • 1 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 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
  • 11 Aug 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
  • 7 Aug 26 0
    • Tool “report_activity” rewrote its description, which is the text the model reads security
    • Schema quality: 67 → 84 ▼ functional
    • Schema quality: good → excellent functional
    • New tool “check_payment_allowed” functional
    • New tool “get_my_identity” functional
    • New tool “get_payment_whitelist” functional
    • New tool “payment_incoming” functional
    • New tool “payment_required” functional
    • New tool “payment_status” functional
  • 3 Aug 26 0
    • Schema quality: 54 → 67 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: excellent → good functional
    • New tool “report_activity” functional
Diagnostics

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 4 Nov 2026 · Probed https://mcp.tracea.online/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.tracea.online CN=YR2,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 RSA 4096 SHA256-RSA 69d94074a8cd84ad9feeebbe45a7363eaa2
SANs: mcp.tracea.online
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.tracea.online. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
online. present 30961 13 Verified
tracea.online. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.tracea.online/mcp Verified 200
http (plaintext) http://mcp.tracea.online/mcp HTTPS enforced 301 https://mcp.tracea.online/mcp
MCP tools · 23 exposed · ~2,307 tokens

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 →

Tool Tokens
check_payment_allowed ~99

Dry-run a payment BEFORE executing it: checks on-chain whether the agent's smart account would allow it (permission granted, within financial cap, destination approved if a whitelist exists). Returns { allowed, reason }.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent (its smart account address)
amount_ethstringyesAmount in ETH, e.g. '0.001'
destinationstringyesDestination address to pay

No output schema declared.

No examples provided.

get_action ~47

Read a single logged agent action from the Tracea ActionLog contract by its numeric ID. Returns agent, action type, payload and timestamp.

NameTypeReqDescription
action_idintegeryesNumeric action ID

No output schema declared.

No examples provided.

get_agent_actions ~37

List all on-chain action IDs logged for a given agent on Tracea.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent

No output schema declared.

No examples provided.

get_agent_info ~46

Get the raw Tracea registry record for an agent: owner, permission scope, financial cap, active status, timestamps.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent

No output schema declared.

No examples provided.

get_my_identity ~101

Get this agent's full Tracea identity (activity apiKey +, for v2 agents, its EOA private key and ERC-4337 smart account address) using a one-time activation code from the owner. The private key is returned ONLY ONCE — save it securely.

NameTypeReqDescription
activation_codestring–One-time activation code (or use ?code= / x-activation-code)
agent_addressstringyesEthereum address of this agent

No output schema declared.

No examples provided.

get_owner_agents ~36

List all agent addresses registered on Tracea by a given owner address.

NameTypeReqDescription
owner_addressstringyesEthereum address of the owner

No output schema declared.

No examples provided.

get_payment_whitelist ~62

Get the list of owner-approved payment destination addresses for an agent (anti-injection guardrail). Non-empty list = the agent's smart account can ONLY pay these addresses. Empty = all allowed.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent

No output schema declared.

No examples provided.

get_registration_file ~47

Fetch the ERC-8004 compatible registration file for a Tracea-registered agent, including the KYA legal principal block.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent

No output schema declared.

No examples provided.

get_verification_card ~152

Get the public URL of an agent's Tracea KYA verification card — the shareable page that presents the mandant entity, the permission scope, the financial cap and a proof hash, with a bilingual FR/EN transparency statement. Use it to hand a verifier a link. Returns the ready-to-share link plus the machine-readable JSON endpoints. Defaults to the 'standard' disclosure level, which is what the API exposes publicly.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent (0x...)
langstring–Card language; the card also auto-detects the visitor's browser language
niveaustring–Disclosure level: minimum | standard (default) | complet

No output schema declared.

No examples provided.

is_agent_revoked ~45

Check whether an agent's mandate has been revoked on Tracea (immediate, scheduled or partial revocation).

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent

No output schema declared.

No examples provided.

log_action ~96

Log an agent action on-chain via Tracea (immutable audit trail, court-ready). Requires TRACEA_API_KEY env var. The action is signed by the account's wallet.

NameTypeReqDescription
action_typestringyesShort action type, e.g. 'email_sent', 'payment_initiated'
agent_addressstringyesEthereum address of the acting agent
datastring–Optional human-readable payload (JSON string recommended)

No output schema declared.

No examples provided.

payment_incoming ~116

Verify a x402 payment ON-CHAIN (the USDC transfer to your address, exact amount) and mark the session fulfilled. The blockchain is the ONLY source of truth — the payment_sessions table is never trusted alone. Returns { status: 'fulfilled', resource } if verified, or an error if not yet paid/expired.

NameTypeReqDescription
payment_idstringyesThe paymentId returned by payment_required (pay_...)
tx_hashstringyesThe on-chain transaction hash of the USDC transfer / payX402 call

No output schema declared.

No examples provided.

payment_required ~195

Create a x402 payment request (HTTP 402) for a resource you sell to another agent. Returns a paymentId, the USDC amount in units, the destination address and the TraceaPayments contract to call. The paying agent must then call TraceaPayments.payX402(destination, amount, paymentId) on-chain — the contract enforces financial cap + whitelist on-chain. Deliver the resource only after payment_incoming confirms fulfilment.

NameTypeReqDescription
agentstring–Address of the paying agent, if known
amount_usdcstringyesAmount in USDC, e.g. '0.50' or '2'
destinationstringyesAddress that receives the USDC payment (yours)
resourcestring–Identifier/URL of the resource to unlock after payment
ttl_secondsnumber–Validity of the payment session (30-3600s, default 300)

No output schema declared.

No examples provided.

payment_status ~66

Get the status of a x402 payment session (pending | paid | fulfilled | expired), with destination, amount and tx hash. Useful to poll while waiting for the paying agent's on-chain transaction.

NameTypeReqDescription
payment_idstringyesThe paymentId returned by payment_required (pay_...)

No output schema declared.

No examples provided.

report_activity ~190

Report an action the agent just performed to its owner's Tracea activity feed (off-chain, free, instant). Call this AFTER every significant action (email sent, message posted, file modified, payment, purchase, booking...). Auth via the Tracea MCP URL (?key=...) from the agent's identity page, OR self-activate with a one-time activation code (?code=... or x-activation-code header) — the tool then receives its apiKey automatically.

NameTypeReqDescription
agent_addressstringyesEthereum address of this agent
categorystringyesAction category
detailsstring–Optional JSON string with extra context
in_permissionboolean–false if this action is OUTSIDE the granted permissions (flagged red)
permission_labelstring–Which owner-granted permission this action falls under
summarystringyesShort human-readable summary of what was done

No output schema declared.

No examples provided.

tracea_anchor_demarche ~128

Seal a validated file as an immutable on-chain proof (Tracea Online, Base). Call this ONLY after tracea_check_demarche returned ok:true — it re-checks everything before anchoring. Requires the caller to be an authorized harness. Returns the proof fingerprint and the record hash.

NameTypeReqDescription
agentstringyesEthereum address (0x...) of the agent smart account that judged the file compliant
donneesobjectyesSame data object that passed tracea_check_demarche
idintegeryesProcedure id (e.g. 15776)

No output schema declared.

No examples provided.

tracea_check_demarche ~142

THE anti-rejection check. Submit the data you collected; it validates every field against the official procedure schema AND cross-checks critical values against official French registries (e.g. SIRET against INSEE Sirene). Returns { ok: true, recordHash } or { ok: false, errors: [{ field, message }] }. ALWAYS call this BEFORE telling the user the file is ready, and fix the exact fields reported.

NameTypeReqDescription
donneesobjectyesCollected data as a flat object, field names exactly as in tracea_demarche_schema
idintegeryesProcedure id (e.g. 15776)

No output schema declared.

No examples provided.

tracea_demarche_document ~186

Prepare le document officiel d'une demarche (CERFA ou demarche libre) et le rend signable. Appelle le generateur du backend Tracea, enregistre le dossier pour l'agent du visiteur et renvoie la reference + le chemin du PDF. A appeler APRES tracea_check_demarche (ok:true) et AVANT tracea_signature. Si des champs manquent, renvoie ok:false + champsManquants : ne fabrique jamais un document partiel.

NameTypeReqDescription
agentstringyesAdresse Ethereum (0x...) de l'agent du visiteur, celle de l'identite de la conversation. Ne jamais l'inventer.
donneesobjectyesDonnees validees, memes champs que tracea_demarche_schema
idintegeryesProcedure id (ex: 26002)

No output schema declared.

No examples provided.

tracea_demarche_preuve ~93

Verify an existing proof: was this file really anchored, when, by which operator, and under which rule version? Use the recordHash returned by tracea_check_demarche / tracea_anchor_demarche. Read-only and free.

NameTypeReqDescription
hashstringyesrecordHash (0x... 32 bytes) returned by tracea_check_demarche or tracea_anchor_demarche

No output schema declared.

No examples provided.

tracea_demarche_schema ~89

Return exactly which fields a given administrative procedure requires (name, type, required, format/pattern, bounds, example). Call this after tracea_list_demarches so you ask the user ONLY for the real fields, in the right format. Prevents hallucinated fields.

NameTypeReqDescription
idintegeryesProcedure id returned by tracea_list_demarches (e.g. 15776)

No output schema declared.

No examples provided.

tracea_list_demarches ~67

List the administrative procedures Tracea supports. ALWAYS call this first: it returns the exact procedure IDs so the AI never has to guess which form (CERFA) applies. `schemaPret: true` means guided mode (anti-rejection check available) is ready for that procedure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

tracea_signature ~188

DEPOSE REELLEMENT le document prepare dans Tracea Sign : cree les signataires, place la zone de signature, produit un lien de signature par personne et envoie les invitations. Exige pdfPath et signataires. Sans eux, aucun lien n'est renvoye.

NameTypeReqDescription
boxstring–Zone de signature 'x,y,w,h' (defaut: detection sur le PDF)
envoyerboolean–Envoyer les invitations (defaut: true)
idinteger–Procedure id (informatif)
niveaustring–Environnement — demo par defaut
pdfPathstring–Chemin du PDF prepare, ex: /root/workspaces/<id>/attestation.pdf
signatairesarray–Adresses e-mail des signataires
titrestring–Titre du document vu par le signataire

No output schema declared.

No examples provided.

verify_agent ~79

Verify an AI agent's on-chain legal identity on Tracea (Base Sepolia). Returns registration status, financial cap, permission scope, revocation status, and KYA legal identity (mandant) when available. Use this BEFORE trusting or delegating work to an agent.

NameTypeReqDescription
agent_addressstringyesEthereum address of the agent (0x...)

No output schema declared.

No examples provided.

Install

How do I install the Tracea MCP server?

Tracea is a hosted endpoint at https://mcp.tracea.online/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 · mcp.tracea.online

# add to Claude Code
claude mcp add --transport http chriscorp-tracea 'https://mcp.tracea.online/mcp'
Common questions

What is the Tracea MCP server?

Tracea is an MCP server listed in the public MCP registry as io.github.Chriscorp/tracea. Tracea, legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible. This page covers its hosted endpoint (https://mcp.tracea.online/mcp).

Is the Tracea MCP server safe to use?

Tracea scores 80 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 Tracea MCP server expose?

Tracea exposes 23 tools: verify_agent, get_agent_info, is_agent_revoked, get_owner_agents, get_action, and 18 more. Their descriptions and schemas cost roughly 2,307 tokens of context every time the server is loaded.

Does the Tracea MCP server require authentication?

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

Is the Tracea MCP server still maintained?

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