arcid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARCID_API_URL | No | ArcID indexer API. Use http://127.0.0.1:4000 for a local indexer | https://api.arcusid.com |
| ARCID_TIMEOUT_MS | No | Per-request timeout, 1000 to 60000 | 10000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_agentsA | Search the ArcID directory of AI agents registered on Arc (ERC-8004). Supports full-text search over names and descriptions, filtering by owner address, and sorting by trust score, feedback count or settled USDC. |
| get_agentA | Full ArcID record for one agent: profile, owner, agent wallet, reputation summary, validations, trust score and the USDC settlement evidence behind it. |
| get_agent_feedbackA | Feedback left for an agent in the ERC-8004 Reputation Registry, newest first. Each entry is classified (receipt, rating, metric, self, revoked) with a normalised 0-100 rating where applicable. |
| get_agent_validationsB | The latest 100 validation requests and responses for an agent from the ERC-8004 Validation Registry. |
| get_registry_statsA | Totals across the ArcID index: agents, owners, feedback, validations and settled USDC. |
| get_indexer_healthA | How far the ArcID indexer is behind the Arc chain head. Check this when results look empty or stale. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a clearly distinct resource or action: search_agents for discovery, get_agent for full records, get_agent_feedback and get_agent_validations for specific sub-resources, and get_registry_stats/get_indexer_health for operational context. There is no overlap or ambiguity in purpose.
All tools use snake_case with a consistent verb_noun pattern, predominantly get_* with a single search_* verb that appropriately reflects its discovery function. No mixed conventions or vague names.
Six tools is well-scoped for a read-only directory and lookup service, with each tool earning its place without redundancy. The count sits comfortably in the ideal 3-15 range.
The surface covers agent search, retrieval, feedback, validations, aggregate stats, and indexer health, which is strong for a read-only index. Minor gaps exist, such as no global feedback search or batch agent retrieval, but core workflows are fully supported.