
Mcp Server
Give agents on-chain smart accounts, micropayments (x402), reputation, and service discovery without bespoke Web3 glue code.
Overview
Azeth MCP is an MCP server for the Build phase that exposes smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents.
What is this MCP server?
- Smart account tooling for AI agents with configurable chain targets (base, ethereum, sepolia variants)
- x402 payment flows and on-chain reputation hooks exposed via MCP
- Service discovery for agent-to-agent or agent-to-protocol capabilities
- npm @azeth/mcp-server v0.2.22 with optional guardian co-signing for spend limits
- Private key auto-generation path to ~/.azeth/key when AZETH_PRIVATE_KEY unset
- npm package @azeth/mcp-server version 0.2.22
- Supported chain env values include base, baseSepolia, ethereum, ethereumSepolia (default baseSepolia)
- Optional AZETH_GUARDIAN_KEY and AZETH_GUARDIAN_AUTO_SIGN for limit overrides
What problem does it solve?
Building agents that pay, get rated, or discover on-chain services means fragile custom wallet code and protocol wiring outside your core product.
Who is it for?
Solo builders shipping agent-native Web3 features (micropayments, discoverable agent services) on Base or Ethereum family chains.
Skip if: Typical indie SaaS with card billing only, or anyone uncomfortable managing private keys and chain RPC setup.
What do I get? / Deliverables
After configuration, your agent can call MCP tools for Azeth smart accounts, payments, reputation, and discovery on your chosen chain.
- Agent-accessible smart account and payment primitives
- Reputation and discovery hooks for agent marketplaces
- Configurable multi-chain Azeth integration from the IDE
Recommended MCP Servers
Journey fit
Integrations is the canonical shelf for wiring external protocols—Azeth is blockchain and payment plumbing for agent products. Smart accounts, x402, and discovery are integration concerns you add while building agent backends, not launch marketing tasks.
How it compares
On-chain agent payments MCP, not a traditional finance dashboard or social distribution tool.
Common Questions / FAQ
Who is Azeth MCP for?
Developers building AI agents that need smart accounts, x402-style payments, reputation, or on-chain service discovery.
When should I use Azeth MCP?
Use during build when integrating paid or trust-based agent capabilities on supported chains, before you ship agent commerce flows.
How do I add Azeth MCP to my agent?
Install @azeth/mcp-server, set AZETH_CHAIN and key-related env vars (and optional guardian/RPC vars), then register the stdio server in your MCP client.