# lcas (remote · lcas.cloud)

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

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `lcas.cloud`: 67/100 (this document), [markdown](https://verifymcp.io/servers/cloud-lcas-directory/lcas.md), [page](https://verifymcp.io/servers/cloud-lcas-directory/lcas)

## Channel facts

- Endpoint: `https://lcas.cloud/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 948 tokens (~189/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the lcas MCP server?

lcas is a hosted endpoint at https://lcas.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

```json
{
  "servers": {
    "cloud-lcas-directory": {
      "type": "http",
      "url": "https://lcas.cloud/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cloud-lcas-directory]
url = "https://lcas.cloud/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-lcas-directory": {
      "type": "remote",
      "url": "https://lcas.cloud/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloud-lcas-directory --url 'https://lcas.cloud/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cloud-lcas-directory:
    url: "https://lcas.cloud/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cloud-lcas-directory": {
      "Transport": "http",
      "Url": "https://lcas.cloud/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloud-lcas-directory -t streamable-http -u 'https://lcas.cloud/mcp'
```

### Other

```json
{
  "mcpServers": {
    "cloud-lcas-directory": {
      "type": "http",
      "url": "https://lcas.cloud/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 67, +1)

- [functional] Server version: 1.3.0 → 1.4.0

### 2026-11-04 (score 66, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 544 → 948
- [functional] Server version: 1.1.0 → 1.3.0
- [functional] New tool “check_agent”
- [functional] New tool “find_tools”
- [cosmetic] “search_agents” added an optional parameter “tested_only”

### 2026-11-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 65, −1)

- [security] Tool “get_agent” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 147 → 181
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “search_agents” added an optional parameter “money”

### 2026-11-01 (score 66)

First indexed and scored.

## MCP tools (5)

### `search_agents` (~273 tokens)

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.

Input parameters:

- `chain` (integer): Chain ID: 1 = Ethereum, 8453 = Base. Omit for both.
- `cursor` (integer): next_cursor from the previous page.
- `limit` (integer)
- `money` (string): Money hint: moves = a tool or skill says it moves funds (transfer, swap, trade, ...); pays = asks the caller for payment (x402 or HTTP 402); reads = prices, balances, tokenized assets. Word matches,…
- `query` (string): Words to match in names, descriptions, MCP tool names and A2A skill names. Omit to list all.
- `service` (string): Only agents that declare this service type.
- `tested_only` (boolean): Only agents whose last weekly live test passed: lcas called one read-only MCP tool or sent one A2A skill example and got an answer.
- `working_only` (boolean): Only agents whose MCP, A2A or web endpoint passed its last check (of `service`, if set). OASF is a description, never checked.

### `find_tools` (~207 tokens)

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.

Input parameters:

- `chain` (integer): Chain ID: 1 = Ethereum, 8453 = Base. Omit for both.
- `limit` (integer)
- `money` (string): Money hint on the tool's own text: moves funds, asks for payment, or reads prices/balances. Word matches, not verified.
- `query` (string, required): Words to match in tool or skill names and descriptions, e.g. "weather forecast".
- `service` (string): Only MCP tools or only A2A skills.
- `tested_only` (boolean): Only endpoints whose last weekly live test passed.

### `get_agent` (~127 tokens)

Get agent

Details of one agent: each declared endpoint with lcas's check result and 30-day history, 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).

Input parameters:

- `agent_id` (string, required): The agent's token ID in the ERC-8004 Identity registry.
- `chain_id` (integer, required): 1 = Ethereum, 8453 = Base.

### `check_agent` (~117 tokens)

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.

Input parameters:

- `agent_id` (string, required): The agent's token ID in the ERC-8004 Identity registry.
- `chain_id` (integer, required): 1 = Ethereum, 8453 = Base.

### `directory_status` (~20 tokens)

Directory status

Which chains lcas indexes and how far each is synced.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cloud-lcas-directory/lcas#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 65
- 2026-11-01: 66

## Common questions

### What is the lcas MCP server?

lcas is an MCP server listed in the public MCP registry as cloud.lcas/directory. Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer. This page covers its hosted endpoint (https://lcas.cloud/mcp).

### Is the lcas MCP server safe to use?

lcas scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the lcas MCP server expose?

lcas exposes 5 tools: search_agents, find_tools, get_agent, check_agent, directory_status. Their descriptions and schemas cost roughly 744 tokens of context every time the server is loaded.

### Does the lcas MCP server require authentication?

No. We connected to lcas without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the lcas MCP server still maintained?

lcas is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://lcas.cloud/mcp
- Website: https://lcas.cloud/docs
- Changelog RSS feed: https://verifymcp.io/servers/cloud-lcas-directory/lcas.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloud-lcas-directory/lcas.json
- HTML version of this page: https://verifymcp.io/servers/cloud-lcas-directory/lcas