Arc Agents MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVM_PRIVATE_KEY | Yes | Private key (`0x` + 64 hex characters) of the dedicated payment wallet. | |
| ARCAGENTS_STATE_DIR | No | Private directory where signed but unresolved payments are saved (one file per request), so they are resent, not replaced, after a restart. Must be an absolute path (a relative path or `~` is rejected at startup) and only readable by you; on Windows that needs a restrictive ACL. | ~/.arcagents-mcp |
| ARCAGENTS_TIMEOUT_MS | No | Total timeout for one tool call, in milliseconds (1000-120000). | 30000 |
| ARCAGENTS_MAX_PAYMENTS | No | Maximum payments this server process may sign (integer 1-1000). At $0.002 each, the default caps a session at $0.10. | 50 |
| ARCAGENTS_PAYMENT_NETWORK | No | Preferred payment network: `arc` or `base`. Any other value stops startup. | arc |
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 |
|---|---|
| get_agent_dataA | Get ERC-8004 agent data from Arc Mainnet for one agent ID: identity and registration (owner, agent wallet, metadata URI, registries), parsed metadata (name, description, services), reputation and feedback, validation data, explorer links and fetch timestamp. Some fields may be unavailable depending on the registry deployment; the API's error information is preserved. Costs $0.002 USDC per successful request, paid automatically with x402 on Arc. |
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 1 tool
With a single tool there is no possibility of tool misselection; an agent cannot confuse it with anything else. The tool's purpose (fetch ERC-8004 agent data by ID) is unambiguous and clearly scoped.
The lone name get_agent_data follows a clean snake_case verb_noun convention consistent with the parameter naming (agentId). There is no mixed convention to cause confusion.
One tool is defensible for a narrow, paid single-endpoint data API, and the tool is a rich composite rather than trivial. However, a one-tool surface for a server branded around 'Agents' feels thin and leaves no room for companion operations like listing or discovery.
For a known agent ID, the fetch is comprehensive (identity, metadata, reputation, validation, explorer links). The surface has no enumeration or search path, so an agent that does not already know the token ID hits a dead end.