lcas

cloud.lcas/directoryVersion 1.7.0

Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer.

Status

Responds265 msNov 14, 2026, 13:42 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:42 UTC
Latency: 265 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://lcas.cloud/mcpResponds265 msNov 14, 2026, 13:42 UTC

No sign-in

Claude Code

claude mcp add --transport http directory https://lcas.cloud/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: directory
Remote MCP server URL: https://lcas.cloud/mcp

Cursor

{
  "mcpServers": {
    "directory": {
      "url": "https://lcas.cloud/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"directory","type":"http","url":"https://lcas.cloud/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

6 tools

Tools of lcas
	Description		Read-only	Idempotent	Open world
`check_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 problems, warnings, tips and passes, each with a suggested fix. Use it to see why an agent is not listed or not working in lcas. Built from stored checks; nothing is re-checked.	Report card for one agent, written for its operator: what lcas found when it last read the registration file and checked each endpoint, as problems, warnings, tips and passes, each with a suggested fix. Use it to see why an agent is not listed or not working in lcas. Built from stored checks; nothing is re-checked.	No	Yes	Yes	No
`check_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 tool list last changed, a tools_pin (save it when you approve the tools; a different pin later means lcas read a changed list), tools whose text matched the tool-poisoning scan, the live and guard tests, and the listed agents that declare the URL. No matches means no listed agent declares this URL, which says nothing about it. Built from stored checks; nothing is called.	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 tool list last changed, a tools_pin (save it when you approve the tools; a different pin later means lcas read a changed list), tools whose text matched the tool-poisoning scan, the live and guard tests, and the listed agents that declare the URL. No matches means no listed agent declares this URL, which says nothing about it. Built from stored checks; nothing is called.	No	Yes	Yes	No
`directory_status`Which chains lcas indexes and how far each is synced.	Which chains lcas indexes and how far each is synced.	No	Yes	Yes	No
`find_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 reliability, not by a score: endpoints whose weekly live test passed first, then by days working in the last 30, then by how well the words match. Each result has the endpoint to connect to and its check history.	Find single MCP tools or A2A skills that do something, across all agents. Only endpoints that passed lcas's last daily check. Ordered by reliability, not by a score: endpoints whose weekly live test passed first, then by days working in the last 30, then by how well the words match. Each result has the endpoint to connect to and its check history.	No	Yes	Yes	No
`get_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 owner holds it, the weekly live test where one exists (one read-only tool called, or one skill example sent), its MCP tools or A2A skills, copies, feedback counts per tag, and money hints (tools that move funds, payment asked, owner wallet kind: wallet, Safe multisig or contract).	Details of one agent: each declared endpoint with lcas's check result, 30-day history and all-time working days, since when the current owner holds it, the weekly live test where one exists (one read-only tool called, or one skill example sent), its MCP tools or A2A skills, copies, feedback counts per tag, and money hints (tools that move funds, payment asked, owner wallet kind: wallet, Safe multisig or contract).	No	Yes	Yes	No
`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 last check. Use get_agent for full details.	Search the lcas directory of ERC-8004 agents. Returns newest first, one entry per group of copies, with which service types passed lcas's last check. Use get_agent for full details.	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 10, 2026
Updated: Nov 10, 2026
Website: https://lcas.cloud/docs⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing