Tracea
REMOTE · MCP.TRACEA.ONLINE · SCANNED SEP 20
Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.
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 Security57
- 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 15 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1262 tokens (~84/item across 15 items; 15 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
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
claude mcp add --transport http chriscorp-tracea 'https://mcp.tracea.online/mcp'
{
"mcpServers": {
"chriscorp-tracea": {
"url": "https://mcp.tracea.online/mcp"
}
}
} {
"servers": {
"chriscorp-tracea": {
"type": "http",
"url": "https://mcp.tracea.online/mcp"
}
}
} [mcp_servers.chriscorp-tracea] url = "https://mcp.tracea.online/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"chriscorp-tracea": {
"type": "remote",
"url": "https://mcp.tracea.online/mcp",
"enabled": true
}
}
} openclaw mcp add chriscorp-tracea --url 'https://mcp.tracea.online/mcp' --transport streamable-http
mcp_servers:
chriscorp-tracea:
url: "https://mcp.tracea.online/mcp" {
"McpServers": {
"chriscorp-tracea": {
"Transport": "http",
"Url": "https://mcp.tracea.online/mcp"
}
}
} assistant mcp add chriscorp-tracea -t streamable-http -u 'https://mcp.tracea.online/mcp'
{
"mcpServers": {
"chriscorp-tracea": {
"type": "http",
"url": "https://mcp.tracea.online/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.
- 1 Sept 26 +1
- Stability: 0.97 → pass security
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 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
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 20 Sept 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=YR1,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | RSA 4096 | SHA256-RSA | 54765fb22ef40aafafbd58d38a5ba60e6eb |
| SANs: mcp.tracea.online | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 |
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 →
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 }.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent (its smart account address) |
| amount_eth | string | yes | Amount in ETH, e.g. '0.001' |
| destination | string | yes | Destination 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | integer | yes | Numeric 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| activation_code | string | – | One-time activation code (or use ?code= / x-activation-code) |
| agent_address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum 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.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | Short action type, e.g. 'email_sent', 'payment_initiated' |
| agent_address | string | yes | Ethereum address of the acting agent |
| data | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Address of the paying agent, if known |
| amount_usdc | string | yes | Amount in USDC, e.g. '0.50' or '2' |
| destination | string | yes | Address that receives the USDC payment (yours) |
| resource | string | – | Identifier/URL of the resource to unlock after payment |
| ttl_seconds | number | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of this agent |
| category | string | yes | Action category |
| details | string | – | Optional JSON string with extra context |
| in_permission | boolean | – | false if this action is OUTSIDE the granted permissions (flagged red) |
| permission_label | string | – | Which owner-granted permission this action falls under |
| summary | string | yes | Short human-readable summary of what was done |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | Ethereum address of the agent (0x...) |
No output schema declared.
No examples provided.
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 15 tools: verify_agent, get_agent_info, is_agent_revoked, get_owner_agents, get_action, and 10 more. Their descriptions and schemas cost roughly 1,262 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.