$ loading_
Enable AI agents with smart accounts, on-chain payments, reputation, and discovery.
This MCP tool comes from an official registry and is open source, giving it generally good auditability. The main security considerations are its requirement for multiple highly sensitive blockchain-related secrets and its ability to execute code locally; remote hosts and data access scope are not clearly disclosed and should be verified before deployment.
It requires highly sensitive secrets such as AZETH_PRIVATE_KEY, AZETH_GUARDIAN_KEY, and XMTP_ENCRYPTION_KEY, plus RPC/service configuration variables. Exposure of such keys could directly enable abuse of on-chain identity, signing, or fund-related actions. The materials do not describe secret storage, least-privilege handling, or rotation practices.
The materials list remote endpoint hosts as 'none', but the environment variables include AZETH_RPC_URL_BASE_SEPOLIA and AZETH_SERVER_URL, and the description implies on-chain interactions, payments, and service discovery. This suggests it likely connects to user-configured RPC or service endpoints. Because no concrete hosts, transmitted data types, or user-data forwarding behavior are disclosed, the actual egress targets and data scope should be verified at deployment time.
The system flags this tool as executes-code, meaning it runs locally as an executable MCP service and has the normal local code-execution capability required for its declared function. Based on the available materials, there is no explicit sign of system-level privileges beyond its intended use, but it should still be isolated and audited as a local executable.
The materials do not explicitly state which local files or persistent data it can read or write, but as a locally running MCP process it will at minimum have access to injected environment variables and runtime context. There is no clear red flag for excessive filesystem or unrelated resource access, but the data-access boundary is under-disclosed and should be constrained through sandboxing, minimal file permissions, and account isolation.
It comes from an official registry, has a public source repository, and has been updated within the last year, all of which materially reduce supply-chain risk through auditability and ongoing maintenance. Community adoption is low and the license is unspecified, which adds some uncertainty, but there is no clear supply-chain red flag in the provided evidence.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.azeth-protocol/mcp-server" MCP server from askskill: Run: claude mcp add 'io-github-azeth-protocol-mcp-server' -- npx -y @azeth/mcp-server
Explain how to use io.github.azeth-protocol/mcp-server to set up an x402 payment flow for my AI agent, including account creation, payment verification, and callback handling.
A setup guide covering smart account configuration, payment verification logic, and key implementation details.
Use io.github.azeth-protocol/mcp-server to retrieve the on-chain reputation of a specific AI agent and summarize the key indicators for risk evaluation.
A summary of the agent's reputation data and the indicators useful for assessing trust and risk.
Use io.github.azeth-protocol/mcp-server to search for AI agent services with specific capabilities, then organize the results by reputation, payment method, and use case.
A service discovery list that compares agent services by capability, trust level, and payment options.
Connect AI agents to non-custodial staking data across 130+ networks.
Connect AI agents to AP2 for payment authorization, audit, and trust workflows.
Enable non-custodial USDC payments on Base for AI agents via MCP.
Enable agent reputation staking with collateral, slashing, and long-term trust building.
Coordinate AI agents through negotiation for more efficient automated workflows.
Connect multiple agent payment protocols for unified charging and settlement workflows.