Categories › AI & Agents › Multi-agent, orchestration & workflows
Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer.
Remote server: your requests and data go to lcas.cloud. Claude Code: claude mcp add --transport http lcas https://lcas.cloud/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_agents — Search the lcas directory of ERC-8004 agents. Returns newest first, one entry per group of copies, with which service types passed lcas's lafind_tools — Find single MCP tools or A2A skills that do something, across all agents. Only endpoints that passed lcas's last daily check. Ordered by relget_agent — Details of one agent: each declared endpoint with lcas's check result, 30-day history and all-time working days, since when the current ownecheck_agent — Report card for one agent, written for its operator: what lcas found when it last read the registration file and checked each endpoint, as pcheck_endpoint — What lcas has stored about one MCP, A2A or web endpoint URL, for a client about to connect to it: last check and 30-day history, when its todirectory_status — Which chains lcas indexes and how far each is synced.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.