lcas
Server Details
Find ERC-8004 agents on Ethereum and Base whose MCP or A2A endpoints actually answer.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Most tools target clearly distinct surfaces: agent search, agent details, agent diagnostics, endpoint inspection, tool discovery, and directory status. The main overlap is between get_agent and check_agent, since both inspect one agent and include check-related information, though check_agent is framed as a focused report card for troubleshooting.
All names use snake_case, which gives a predictable baseline. The verb choices vary slightly for similar discovery actions (search_agents vs find_tools) and directory_status is a noun phrase, but the set remains readable and mostly consistent.
Six tools is well-scoped for a directory and inspection server. Each tool covers a distinct layer: agents, endpoints, tools, and overall directory status.
The read-only surface covers agent discovery, agent details, diagnostics, endpoint checks, tool search, and directory sync status. Minor gaps exist around direct endpoint browsing or dedicated tool-detail lookup beyond find_tools results, but core workflows are covered.
Available Tools
6 toolscheck_agentCheck agent listingARead-onlyIdempotentInspect
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.
Inputs: agent_id (required), chain_id (required).
check_endpointCheck endpoint URLARead-onlyIdempotentInspect
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.
Inputs: url (required).
directory_statusDirectory statusBRead-onlyIdempotentInspect
Which chains lcas indexes, how far each is synced, and how many agents are hidden by content moderation.
Inputs: no named parameters.
find_toolsFind toolsARead-onlyIdempotentInspect
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.
Inputs: query (required), chain, limit, money, +3 more.
get_agentGet agentBRead-onlyIdempotentInspect
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).
Inputs: agent_id (required), chain_id (required).
search_agentsSearch agentsARead-onlyIdempotentInspect
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.
Inputs: chain, limit, money, query, +8 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Checks whether an ERC-8004-registered agent is actually alive right now via a real MCP handshake
On-chain ERC-8004 agent registry. Search, register, and check reputation across 16 chains.
Look up AI agents, MCP servers and x402 APIs: whether they answer, how they ask to be paid.
Evidence about ERC-8004 agents on BNB Smart Chain, gathered by calling them. No key.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceEnables users to verify whether an ERC-8004-registered agent is currently reachable by resolving its on-chain registration and performing a live MCP handshake, returning verdicts such as REGISTERED_UNREACHABLE or AGENT_NOT_FOUND.-
- AlicenseNot gradedqualityBmaintenanceLets you probe ERC-8004 agents on BNB Smart Chain by calling their declared MCP or A2A endpoints, checking payment requirements, reading on-chain reputation authorship, and finding agents by description.MIT
- AlicenseAqualityDmaintenanceAn MCP server that bridges ERC-8004 agent identity, reputation, and validation registries into tool calls, enabling discovery, inspection, and verification of on-chain AI agents from any MCP client.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover and interact with onchain agent infrastructure on Base, including identity, micropayments, and tool capabilities via MCP.4MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.