Amanchain MCP

What amanchain-mcp MCP server does

The amanchain-mcp MCP server provides an MCP catalog and one tool for each of 59 pay-per-call AI services. Available categories include cryptocurrency prices and token audits, whale transaction monitoring, market reports, LLM completions, image generation, web search and fetching, summarization, geolocation, weather, foreign-exchange rates, translation, invoices, and receipts.

The catalog tool lets an agent discover available services before making a paid request. Service prices are supplied by the network and can vary; the current catalog is published through AmanChain's live x402 endpoint. Completed payments produce an on-chain receipt that can be checked through the public receipts ledger.

How it works

The amanchain-mcp MCP server sends each service request to an AmanChain relay endpoint. The relay responds with an x402 challenge containing a signed price. The local process checks that quote against its configured limits, creates an EIP-3009 signature for USDC on Base, and retries the request with the payment signature. The service response is then returned to the MCP client.

Payments use USDC on Base, and the facilitator covers gas for the described gasless flow. The private key stays on the local machine and is used to sign the transfer. Prices are not estimated by the client; they are read from the signed challenge returned by the server.

Setup and configuration

Install the server through an MCP client's stdio configuration with npx -y amanchain-mcp. Claude Code can register it with claude mcp add, while Claude Desktop and Cursor use their MCP configuration files. Set AMAN_PRIVATE_KEY to a Base wallet key for paid calls, and fund that wallet with USDC on Base. The README describes a balance of about one dollar as a starting point.

Without AMAN_PRIVATE_KEY, catalog access, price information, and service discovery still work. Paid requests instead explain what wallet setup is needed. Optional settings include AMAN_ORIGIN, a per-call limit through AMAN_MAX_USD_PER_CALL, a rolling daily limit through AMAN_MAX_USD_PER_DAY, and a custom spend-ledger path through AMAN_SPEND_LEDGER. The default limits are $0.05 per call and $1.00 per day; spending data is persisted in a local ledger by default.

Tools and capabilities

The amanchain-mcp MCP server exposes amanchain_catalog along with service-specific tools. Examples include:

• aman_crypto_price for live cryptocurrency prices
• aman_token_audit for on-chain token information such as backing, flags, holders, and liquidity depth
• aman_market_report for a broader market report
• aman_llm_chat for an LLM completion
• aman_image_gen for image generation
• aman_web_search, aman_web_fetch, and aman_summarize for web workflows
• aman_crypto_whale_watch for whale transaction monitoring
• aman_geo_ip, aman_weather, aman_fx_rates, and aman_translate for utility tasks

Each paid call is priced by the network, and the amount is shown in the x402 response. Spending controls can reject quotes above the configured per-call or daily threshold before payment is made.