# io.github.Chriscorp/tracea

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** io.github.Chriscorp
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.tracea.online/mcp
- **Source:** https://tracea.online
- **Endpoint health:** reachable (last checked 2026-10-03T19:51:29.341Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 13 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-22T12:03:12.446Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

15 declared. Observed from a live `tools/list` probe.
- `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 
- `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).
- `get_owner_agents` — List all agent addresses registered on Tracea by a given owner address.
- `get_action` — Read a single logged agent action from the Tracea ActionLog contract by its numeric ID. Returns agent, action type, payload and timestamp.
- `get_agent_actions` — List all on-chain action IDs logged for a given agent on Tracea.
- `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.
- `get_registration_file` — Fetch the ERC-8004 compatible registration file for a Tracea-registered agent, including the KYA legal principal block.
- `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, 
- `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 cod
- `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 th
- `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 a
- `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 th
- `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 — th
- `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 payi

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"tracea\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.tracea.online/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.Chriscorp%2Ftracea
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.Chriscorp%2Ftracea/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.Chriscorp%2Ftracea
- HTML page: https://forgeregistry.com/registry/io.github.Chriscorp%2Ftracea
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.