lcas
REMOTE · LCAS.CLOUD
Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Server version: 1.3.0 → 1.4.0 functional
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 544 → 948 ▼ functional
- Server version: 1.1.0 → 1.3.0 functional
- New tool “check_agent” functional
- New tool “find_tools” functional
- “search_agents” added an optional parameter “tested_only” cosmetic
- 3 Nov 26 +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.
- 2 Nov 26 −1
- Tool “get_agent” rewrote its description, which is the text the model reads security
- Schema quality: 147 → 181 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- “search_agents” added an optional parameter “money” cosmetic
- 1 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://lcas.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lcas.cloud | CN=WE1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 49184a5db0e0ecc0e12533366297b53 |
| SANs: lcas.cloud, *.lcas.cloud | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of lcas.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| lcas.cloud. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lcas.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://lcas.cloud/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent Check agent listing ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent's token ID in the ERC-8004 Identity registry. |
| chain_id | integer | yes | 1 = Ethereum, 8453 = Base. |
No output schema declared.
No examples provided.
directory_status Directory status ~20
Which chains lcas indexes and how far each is synced.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_tools Find tools ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
get_agent Get agent ~127
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent's token ID in the ERC-8004 Identity registry. |
| chain_id | integer | yes | 1 = Ethereum, 8453 = Base. |
No output schema declared.
No examples provided.
search_agents Search agents ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · lcas.cloud
claude mcp add --transport http cloud-lcas-directory 'https://lcas.cloud/mcp'
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.