tempo-mcp and mcp-server
These are complements: Tempo enables autonomous stablecoin execution on a specific blockchain, while Azeth provides a broader smart account abstraction layer that could route or manage those payments alongside reputation and discovery services.
About tempo-mcp
arome3/tempo-mcp
MCP server enabling AI agents to execute autonomous stablecoin payments on Tempo blockchain. Supports single/batch payments, scheduled transfers, token swaps, and balance queries with built-in spending limits, audit logging and many more
Implements MCP as a stdio-based server that connects to Tempo's on-chain contracts via RPC, enabling Claude to execute transactions by signing with configured wallet keys (private key, keystore, or external signers like Turnkey). Beyond basic payments, it exposes advanced Tempo protocol features including TIP-403 compliance policies, access key (session key) delegation with per-token spending limits, Fee AMM liquidity provision, and DEX order management including flip orders for automated market making. Integrates directly with Claude Desktop via config file and supports testnet-only experimentation with free faucet tokens.
About mcp-server
azeth-protocol/mcp-server
MCP server for Azeth — smart accounts, payments, reputation, and discovery tools for AI agents
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work