Home / MCP registry index / io.github.Chriscorp/tracea
Tracea
io.github.Chriscorp/tracea in the official MCP registry.
Endpoint https://mcp.tracea.online/mcp.
The registry describes it as: Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.
We read its 23 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
verify_agent get_agent_info is_agent_revoked get_owner_agents get_action get_agent_actions log_action get_registration_file report_activity get_my_identity get_payment_whitelist check_payment_allowed payment_required payment_incoming payment_status tracea_list_demarches tracea_demarche_schema tracea_check_demarche tracea_anchor_demarche tracea_demarche_preuve tracea_demarche_document tracea_signature get_verification_card
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-chriscorp-tracea)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.