Purpose
@azeth/mcp-server is the MCP server for the Azeth protocol, positioned as the trust, discovery, and payment layer of the machine economy. It is aimed at AI agents and provides 32 tools for creating accounts, initiating payments, discovering services, managing reputation, and communicating via XMTP.
Main Capabilities
The tools cover the following areas (based on the example prompts):
- Account management: create new accounts, query balances, list registered accounts, deposit ETH into smart accounts.
- Payments and transfers: pay USDC to a specified party, set up subscription services, transfer ETH.
- Service discovery: find agents with specific capabilities (such as a price feed on Base Sepolia), query available services, view the reputation scores of data providers.
- Communication: send messages via XMTP, check agent reachability, list recent conversations.
- Security and guardrails: view current guardrail settings, whitelist protocols (such as Uniswap).
- Address resolution: supports Ethereum addresses, participant names (resolved via the trust registry), the self-reference "me", and index references (such as "#1" and "#2").
All tools return structured JSON, and errors include machine-readable codes and recovery suggestions.
Usage
No API key is required. Private keys are automatically generated and persisted in ~/.azeth/key, and Gas is automatically sponsored.
Add the configuration to ~/Library/Application Support/Claude/claude_desktop_config.json to use it in the Claude desktop app. After adding it, you can directly say to Claude: "Create me a smart account called PriceFeedBot".
If you need to use it in a production environment or reuse an existing key, you can pass it in via environment variables (all environment variables are optional, and the server can run with zero configuration on the testnet).
Applicable Scenarios
Suitable for development and experimental scenarios that require AI agents to have autonomous accounts, payments, service discovery, and reputation management capabilities, especially in testnet environments where you can get started quickly.
Limitations and Notes
- Using npx as the MCP server launcher has two problems: the installation prompt blocks stdin (sharing stdin with the MCP protocol causes a deadlock), and cold starts require downloading about 142 packagesand timing out. It is recommended to install globally.
- If a "Failed to connect to MCP server" error occurs, it is usually caused by the npx issue described above.
- The documentation does not provide information such as specific fees, prices, platform support scope, or performance guarantees.
