Zero-knowledge MCP secrets vault for AI agents: secrets injected at runtime, never seen by the model
Tracea is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tracea-mcp https://mcp.tracea.online/mcp
# 2 — ask your agent for something these tools do
# verify_agent, get_agent_info, is_agent_revoked and 20 more
Tracea costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tracea-mcp https://mcp.tracea.online/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
23 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent (0x...) |
Get the raw Tracea registry record for an agent: owner, permission scope, financial cap, active status, timestamps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent |
Check whether an agent's mandate has been revoked on Tracea (immediate, scheduled or partial revocation).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent |
List all agent addresses registered on Tracea by a given owner address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| owner_address | string | yes | Ethereum address of the owner |
Read a single logged agent action from the Tracea ActionLog contract by its numeric ID. Returns agent, action type, payload and timestamp.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action_id | integer | yes | Numeric action ID |
List all on-chain action IDs logged for a given agent on Tracea.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the acting agent |
| action_type | string | yes | Short action type, e.g. 'email_sent', 'payment_initiated' |
| data | string | no | Optional human-readable payload (JSON string recommended) |
Fetch the ERC-8004 compatible registration file for a Tracea-registered agent, including the KYA legal principal block.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent |
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 r
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of this agent |
| category | string | yes | Action category |
| summary | string | yes | Short human-readable summary of what was done |
| permission_label | string | no | Which owner-granted permission this action falls under |
| in_permission | boolean | no | false if this action is OUTSIDE the granted permissions (flagged red) |
| details | string | no | Optional JSON string with extra context |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of this agent |
| activation_code | string | no | One-time activation code (or use ?code= / x-activation-code) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent |
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 }.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent (its smart account address) |
| destination | string | yes | Destination address to pay |
| amount_eth | string | yes | Amount in ETH, e.g. '0.001' |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| destination | string | yes | Address that receives the USDC payment (yours) |
| amount_usdc | string | yes | Amount in USDC, e.g. '0.50' or '2' |
| resource | string | no | Identifier/URL of the resource to unlock after payment |
| agent | string | no | Address of the paying agent, if known |
| ttl_seconds | number | no | Validity of the payment session (30-3600s, default 300) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_id | string | yes | The paymentId returned by payment_required (pay_...) |
| tx_hash | string | yes | The on-chain transaction hash of the USDC transfer / payX402 call |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| payment_id | string | yes | The paymentId returned by payment_required (pay_...) |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Procedure id returned by tracea_list_demarches (e.g. 15776) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Procedure id (e.g. 15776) |
| donnees | object | yes | Collected data as a flat object, field names exactly as in tracea_demarche_schema |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Procedure id (e.g. 15776) |
| donnees | object | yes | Same data object that passed tracea_check_demarche |
| agent | string | yes | Ethereum address (0x...) of the agent smart account that judged the file compliant |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hash | string | yes | recordHash (0x... 32 bytes) returned by tracea_check_demarche or tracea_anchor_demarche |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Procedure id (ex: 26002) |
| donnees | object | yes | Donnees validees, memes champs que tracea_demarche_schema |
| agent | string | yes | Adresse Ethereum (0x...) de l'agent du visiteur, celle de l'identite de la conversation. Ne jamais l'inventer. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | no | Procedure id (informatif) |
| pdfPath | string | no | Chemin du PDF prepare, ex: /root/workspaces/<id>/attestation.pdf |
| titre | string | no | Titre du document vu par le signataire |
| signataires | array | no | Adresses e-mail des signataires |
| envoyer | boolean | no | Envoyer les invitations (defaut: true) |
| box | string | no | Zone de signature 'x,y,w,h' (defaut: detection sur le PDF) |
| niveau | string | no | Environnement — demo par defaut |
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 exp
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent (0x...) |
| niveau | string | no | Disclosure level: minimum | standard (default) | complet |
| lang | string | no | Card language; the card also auto-detects the visitor's browser language |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tracea or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| verify_agent | no tags | |
| get_agent_info | no tags | |
| is_agent_revoked | no tags | |
| get_owner_agents | no tags | |
| get_action | no tags | |
| get_agent_actions | no tags | |
| log_action | no tags | |
| get_registration_file | untrusted-input | untrusted-input: keyword "fetch" |
| report_activity | no tags | |
| get_my_identity | no tags | |
| get_payment_whitelist | no tags | |
| check_payment_allowed | no tags | |
| payment_required | no tags | |
| payment_incoming | no tags | |
| payment_status | no tags | |
| tracea_list_demarches | no tags | |
| tracea_demarche_schema | no tags | |
| tracea_check_demarche | no tags | |
| tracea_anchor_demarche | no tags | |
| tracea_demarche_preuve | no tags | |
| tracea_demarche_document | no tags | |
| tracea_signature | no tags | |
| get_verification_card | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tracea can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.