Tracea MCP server
io.github.Chriscorp/traceaChriscorpstreamable-httpv0.1.0Scanned
Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.
23 tools: 3 do something that can't be undone, 8 change things and 12 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Tracea MCP server can do
The Tracea MCP server is published by the GitHub account Chriscorp. It has 23 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_payment_allowed, payment_required and payment_incoming) and create or change data (8 tools: verify_agent, is_agent_revoked, report_activity, tracea_check_demarche and 4 more), but cannot delete data. 12 tools only read.
1 tool reads private data (get_registration_file); 1 tool brings in text other people can write (get_verification_card).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
23 tools
Can't be undone 3Claude Code: ask
check_payment_allowedDry-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 whiteli…No findings
Why it is in this group
- The name "check_payment_allowed" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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 }.
payment_incomingVerify a x402 payment ON-CHAIN (the USDC transfer to your address, exact amount) and mark the session fulfilled.No findings
Why it is in this group
- The name "payment_incoming" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
payment_requiredCreate a x402 payment request (HTTP 402) for a resource you sell to another agent.No findings
Why it is in this group
- The name "payment_required" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it 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.
Changes things 8Claude Code: ask
is_agent_revokedCheck whether an agent's mandate has been revoked on Tracea (immediate, scheduled or partial revocation).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Check whether an agent's mandate has been revoked on Tracea (immediate, scheduled or partial revocation).
report_activityReport an action the agent just performed to its owner's Tracea activity feed (off-chain, free, instant).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
tracea_anchor_demarcheSeal a validated file as an immutable on-chain proof (Tracea Online, Base).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
tracea_check_demarcheTHE anti-rejection check.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
tracea_demarche_documentPrepare le document officiel d'une demarche (CERFA ou demarche libre) et le rend signable.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
tracea_demarche_preuveVerify an existing proof: was this file really anchored, when, by which operator, and under which rule version?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
tracea_signatureDEPOSE 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
verify_agentVerify an AI agent's on-chain legal identity on Tracea (Base Sepolia).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 12Show 12 read-only tools
get_actionRead a single logged agent action from the Tracea ActionLog contract by its numeric ID.No findings
Why it is in this group
- The name "get_action" says "get": a word for reading.
Description, as the server wrote it Read a single logged agent action from the Tracea ActionLog contract by its numeric ID. Returns agent, action type, payload and timestamp.
get_agent_actionsList all on-chain action IDs logged for a given agent on Tracea.No findings
Why it is in this group
- The name "get_agent_actions" says "get": a word for reading.
Description, as the server wrote it List all on-chain action IDs logged for a given agent on Tracea.
get_agent_infoGet the raw Tracea registry record for an agent: owner, permission scope, financial cap, active status, timestamps.No findings
Why it is in this group
- The name "get_agent_info" says "get": a word for reading.
Description, as the server wrote it Get the raw Tracea registry record for an agent: owner, permission scope, financial cap, active status, timestamps.
get_my_identityGet 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.No findings
Why it is in this group
- The name "get_my_identity" says "get": a word for reading.
Description, as the server wrote it 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.
get_owner_agentsList all agent addresses registered on Tracea by a given owner address.No findings
Why it is in this group
- The name "get_owner_agents" says "get": a word for reading.
Description, as the server wrote it List all agent addresses registered on Tracea by a given owner address.
get_payment_whitelistGet the list of owner-approved payment destination addresses for an agent (anti-injection guardrail).No findings
Why it is in this group
- The name "get_payment_whitelist" says "get": a word for reading.
Description, as the server wrote it 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.
get_registration_fileFetch the ERC-8004 compatible registration file for a Tracea-registered agent, including the KYA legal principal block.Reads private dataNo findings
Why it is in this group
- The name "get_registration_file" says "get": a word for reading.
What it can reach
- private-dataThe name "get_registration_file" says "get" and "file": it reads files.
- private-dataThe description's first sentence says "fetch" and "file": it reads files.
Description, as the server wrote it Fetch the ERC-8004 compatible registration file for a Tracea-registered agent, including the KYA legal principal block.
get_verification_cardGet 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 …Reads text others writeNo findings
Why it is in this group
- The name "get_verification_card" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
log_actionLog an agent action on-chain via Tracea (immutable audit trail, court-ready).No findings
Why it is in this group
- The name "log_action" says "log": a word for reading.
Description, as the server wrote it 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.
payment_statusGet the status of a x402 payment session (pending | paid | fulfilled | expired), with destination, amount and tx hash.No findings
Why it is in this group
- The name "payment_status" says "status": a word for reading.
Description, as the server wrote it 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.
tracea_demarche_schemaReturn exactly which fields a given administrative procedure requires (name, type, required, format/pattern, bounds, example).No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
tracea_list_demarchesList the administrative procedures Tracea supports.No findings
Why it is in this group
- The name "tracea_list_demarches" says "list": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 11
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.tracea.online/.well-known/oauth-protected-resource
- Authorization servers
- https://mcp.tracea.online
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 11 tools that change things (3 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.tracea.online/mcp: tools/list returned 23 tools to an anonymous client, including check_payment_allowed (irreversible), payment_required (irreversible), payment_incoming (irreversible), verify_agent (write), is_agent_revoked (write) and 6 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http tracea https://mcp.tracea.online/mcpclaude mcp add --transport http tracea https://mcp.tracea.online/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tracea__get_agent_info",
"mcp__tracea__get_owner_agents",
"mcp__tracea__get_action",
"mcp__tracea__get_agent_actions",
"mcp__tracea__log_action",
"mcp__tracea__get_registration_file",
"mcp__tracea__get_my_identity",
"mcp__tracea__get_payment_whitelist",
"mcp__tracea__payment_status",
"mcp__tracea__tracea_list_demarches",
"mcp__tracea__tracea_demarche_schema",
"mcp__tracea__get_verification_card"
],
"ask": [
"mcp__tracea__verify_agent",
"mcp__tracea__is_agent_revoked",
"mcp__tracea__report_activity",
"mcp__tracea__check_payment_allowed",
"mcp__tracea__payment_required",
"mcp__tracea__payment_incoming",
"mcp__tracea__tracea_check_demarche",
"mcp__tracea__tracea_anchor_demarche",
"mcp__tracea__tracea_demarche_preuve",
"mcp__tracea__tracea_demarche_document",
"mcp__tracea__tracea_signature"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tracea. Review it before you use it.
Capability tags behind 2 rules
- mcp__tracea__get_registration_file private-data
- mcp__tracea__get_verification_card untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Chriscorp/tracea/verify?hash=d107a730b341a6725367487cb5df9b912aa933ccbc3f9a8e8f14a19816476ed8" | jq -e '.changed == false'Pinned hash d107a730b341, from Nov 16, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Chriscorp/tracea/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Chriscorp/tracea)Source: MCP Registry. Synced Oct 21, 2026, 18:15 UTC.
Tracea MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Tracea MCP server safe?
- No scan can promise that. What its definitions show: 23 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Tracea MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Tracea MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: check_payment_allowed, payment_required and payment_incoming.
What tools does the Tracea MCP server have?
- 23 tools: 3 irreversible, 8 write, 12 read. check_payment_allowed, payment_required, payment_incoming, verify_agent, is_agent_revoked, report_activity, tracea_check_demarche, tracea_anchor_demarche and 15 more.
Does the Tracea MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Tracea MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Tracea MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.