Tracea MCP Server

by chriscorp Your server? Claim it

answering

Tracea is answering right now. Last checked 14 min ago. It exposes 15 tools.

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

Uptime history 47 days of history

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

255 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Tracea every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tracea --transport http https://mcp.tracea.online/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "tracea": {
      "url": "https://mcp.tracea.online/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.tracea]
url = "https://mcp.tracea.online/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tracea": {
      "url": "https://mcp.tracea.online/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "tracea": {
      "url": "https://mcp.tracea.online/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

payment

check_payment_allowed

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 }.

get_payment_whitelist

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.

payment_incoming

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_required

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.

payment_status

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.

agent

get_agent_actions

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

get_agent_info

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

is_agent_revoked

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

action

get_action

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

identity

get_my_identity

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.

log

log_action

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.

owner

get_owner_agents

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

registration

get_registration_file

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

report

report_activity

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.

verify

verify_agent

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.tracea.online/mcp	streamable-http	answering	225 ms	14 min ago

Alternatives to Tracea

same job, measured the same way

Myco Brain

by thegoodguysla

Self-hosted, source-traceable memory layer and MCP server for AI agents, on your own Postgres.

66 installs/wk local only

Kakunin

by nqzai

X.509 identity, risk scoring, and audit logging for AI agents. MiCA + EU AI Act compliant.

62 installs/wk local only

Kakunin

by kakunin-ai

X.509 identity, risk scoring, and audit logging for AI agents. MiCA + EU AI Act compliant.

local only

Tru8 Evidence Research

by samyatessmith

Source-traced evidence research for AI agents. We organise the evidence; you decide.

166 installs/wk 3 tools answering

Traced Openai Langchain Agent

by getvda

Traced OpenAI LangChain Agent

2 tools answering

True Memory Fragments

by kyle641320

Detect stale source context and retain traceable code-chain understanding for AI coding agents.

local only

Rune

by thecolourfoundation

Evidence-traced codebase understanding and security scanning for AI agents over MCP.

24 installs/wk local only

The Context Company

by the-context-company

AI agent observability for production traces, natural-language insights, and improvement loops.

answering

Tracea — questions

Answers built from our own checks of this server.

What can Tracea do?

It exposes 15 tools, read directly from the server on our last check. Among them: check_payment_allowed, get_action, get_agent_actions, get_agent_info, get_my_identity, get_owner_agents and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Tracea mostly used for?

Its tools cluster around payment and agent. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Tracea working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 255 ms. The bar chart above shows every period we have measured.

How do I connect Tracea?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Tracea need an API key?

No. Tracea completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Tracea?

It answers our handshake in 255 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.