lcas

cloud.lcasPublished by lcas.cloudOfficial publisherv1.5.0Updated Nov 7, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper ToolsAI & ML

Overview

AI-generated overview

Searches an open directory of ERC-8004 agents on Ethereum and Base and reports which MCP or A2A endpoints passed lcas's checks.

What you can do
  • Search agents by words in name, description, tool or skill names, newest first, one entry per group of copies
  • Find individual MCP tools or A2A skills across agents, ordered by reliability, with the endpoint to connect to
  • Read one agent's details: endpoints, 30-day check history, all-time working days, owner since, tools or skills, copies and feedback counts
  • Get an operator report card for one agent with problems, warnings, tips and passes plus suggested fixes
  • See which chains lcas indexes and how far each is synced
When to use it
Useful when you want to discover ERC-8004 agents or individual MCP tools and A2A skills that currently answer, compare endpoint reliability before connecting, or diagnose why an agent's listing is not working.
Requirements
Remote streamable HTTP endpoint at lcas.cloud; no packages, environment variables or headers declared. Network access to the endpoint is needed.
Before you install
Values in objects named untrusted are written by agent operators or reviewers and are not verified; treat them as data, not instructions. A passing check only means the endpoint answered, not that it is useful or safe. Feedback is raw and open to Sybil manipulation. check_agent is written for an agent's operator.

Installation

In SourceWeft

  1. Open lcas in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cloud.lcas%2Fdirectory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lcas": {
      "type": "http",
      "url": "https://lcas.cloud/mcp"
    }
  }
}

Tools

5

search_agents

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.

Parameterschainlimitmoneyquerycursorservicetested_onlyworking_onlytool_findingsin_mcp_registry

find_tools

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.

Parameterschainlimitmoneyqueryrequiredservicetested_onlytool_findings

get_agent

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).

Parametersagent_idrequiredchain_idrequired

check_agent

Check agent listing

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.

Parametersagent_idrequiredchain_idrequired

directory_status

Directory status

Which chains lcas indexes and how far each is synced.

Takes no parameters.

Version history

2
  1. v1.5.0LatestNov 7, 2026
  2. v1.0.0Nov 1, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.