
Azeth Protocol
io.github.azeth-protocolPublished by GitHub account azeth-protocolv0.2.22Updated Oct 25, 2026
Smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents
Overview
Azeth Protocol lets an AI assistant create on-chain smart accounts, send payments, discover and rate services, and message other agents over XMTP.
- What you can do
- Create and manage smart accounts, check balances and history, deposit funds, and manage token whitelists, plus send ETH or ERC-20 transfers from the account. Pay for x402 services, set up subscriptions and recurring payment agreements, and execute, cancel or query those agreements. Publish, update and discover services on the ERC-8004 trust registry by capability and reputation. Submit and read payment-weighted reputation opinions and net-paid figures. Send and receive end-to-end encrypted XMTP messages, list conversations and check agent reachability. View and change guardian guardrails and protocol whitelists.
- When to use it
- Use it when an assistant needs to act as an autonomous economic agent: paying for services, subscribing to recurring feeds, finding other agents by capability, or exchanging messages with them. It suits testnet experimentation and, with care, real on-chain payments on Base or Ethereum.
- Requirements
- Runs locally as an npm package (global install recommended; npx can deadlock or time out). Node.js and network access to RPC endpoints and the Azeth API. No API keys required; a private key is auto-generated at ~/.azeth/key if AZETH_PRIVATE_KEY is unset. Optional: AZETH_CHAIN, per-chain AZETH_RPC_URL_* variables, AZETH_SERVER_URL, AZETH_GUARDIAN_KEY, AZETH_GUARDIAN_AUTO_SIGN, AZETH_EMERGENCY_ADDRESS, XMTP_ENCRYPTION_KEY.
Installation
In SourceWeft
- Open Azeth Protocol in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@azeth/mcp-server
[mcp-azeth MCP server]MCP (Model Context Protocol) server for Azeth -- the trust, discovery, and payment layer for the machine economy. Provides 32 tools for AI agents to create accounts, make payments, discover services, manage reputation, and communicate via XMTP.
Setup
No API keys required. A private key is auto-generated and persisted at ~/.azeth/key. Gas is sponsored automatically.
Install
Claude Code
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Then ask Claude: "Create me a smart account called PriceFeedBot" -- that's it.
With Your Own Key
For production or to use an existing key, add environment variables:
Environment Variables
All optional. The server works with zero configuration on testnet.
Tools (32)
Example Prompts
Here are example prompts to help AI agents understand when to use each tool:
Account Management
- "Create a new account for my PriceFeedBot service"
- "What's the balance of my main account?"
- "Show me all my registered accounts"
- "Deposit 0.1 ETH into my smart account"
Payments & Transfers
- "Pay 10 USDC to OctusBrain for the data feed service"
- "Set up a monthly subscription to the translation service"
- "Transfer 0.05 ETH to 0x1234...abcd"
Service Discovery
- "Find agents that can do price-feed on Base Sepolia"
- "What services are available for translation?"
- "Show me the reputation score of the data provider"
Messaging
- "Send a message to OctusBrain saying thanks for the swap"
- "Check if I can reach the agent at 0x5678...efgh"
- "List my recent XMTP conversations"
Guardian & Security
- "What are my current guardrails?"
- "Whitelist the Uniswap protocol for swaps"
Address Resolution
All tools that accept addresses support flexible resolution:
- Ethereum address:
0x1234...abcd - Participant name:
"OctusBrain"(resolved via trust registry) - Self-reference:
"me"(your first smart account) - Index reference:
"#1","#2"(by account index)
Response Format
All tools return structured JSON:
Errors include machine-readable codes and recovery suggestions:
Full Documentation
See the Azeth documentation for complete tool reference with parameter tables, return values, and example prompts for all 32 tools.
Troubleshooting
"Failed to connect to MCP server"
If you used npx instead of a global install, npx has two problems as an MCP server launcher:
- Installation prompt blocks stdin —
npxprompts "Ok to proceed? (y)" which reads from the same stdin the MCP protocol uses, deadlocking the connection. - Cold-start download timeout — First run must download ~142 packages before the server can start. Claude's MCP client times out waiting.
Fix by installing globally:
Development
License
MIT
Source: README.md at commit 8bf89ba
Tools
0Version history
1- v0.2.22LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts