# @asterpay/mcp-server

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/timolein74/asterpay-mcp-server  
**Views:** 9  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/-asterpay-mcp-server

## Description
EUR settlement for AI agents via x402 protocol. Market data, AI tools, crypto analytics — pay-per-call in USDC on Base. SEPA Instant EUR off-ramp.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What @asterpay/mcp-server MCP server does

The @asterpay/mcp-server MCP server gives an agent a merchant-facing workflow over MCP. It can retrieve a product catalog, inspect individual products, check inventory, read business policies, create orders, and retrieve order status. Product responses include names, EUR prices, descriptions, availability, and variants. Business information can include operating hours, contact details, delivery zones and fees, return policies, and accepted payment methods.

The server also connects order workflows to the x402 payment protocol. After an order intent is created, the agent can retrieve the facilitator endpoint, USDC amount, network, and payment header needed to execute payment. This makes the server relevant to agents that buy products or call paid APIs rather than only read merchant data.

## How it works

A typical product workflow starts with `list_products`, followed by `get_product` or `check_availability` for a selected product ID. `place_order` creates an intent and submits the order; its response includes x402 payment details for the agent’s payment client. `get_order_status` can then report whether the order is pending, confirmed, rejected, or expired, along with payment information and items.

For paid x402 API calls, `set_budget` activates an AsterPay prepaid budget. An agent can supply an existing `bud_...` token, or a human can first send between 1 and 500 USDC on Base and provide the transaction hash and wallet. Calling the tool without those values returns funding instructions. `get_budget_status` reports the remaining balance, total spending, and recent calls with per-call prices.

## Tools and capabilities

- `list_products`: Retrieves all products offered by a merchant.
- `get_product`: Returns detailed information for a product ID.
- `check_availability`: Reports stock status, quantity, and current price.
- `get_business_info`: Retrieves merchant operations, delivery, returns, and payment information.
- `place_order`: Creates and submits an order, returning x402 payment data.
- `get_order_status`: Checks the current state and payment details of an order.
- `get_x402_payment_details`: Returns the payment data required by an x402 client.
- `set_budget`: Activates an existing prepaid budget or helps create one after human funding.
- `get_budget_status`: Shows available funds and recent paid calls.

## Limitations and notes

The @asterpay/mcp-server MCP server does not let an agent grant itself money. New budget funding requires a one-time human USDC transfer on Base, and the funding wallet is sanctions-screened by Chainalysis.

The server supplies x402 payment details but does not itself execute the payment. An agent needs a compatible x402 client, such as `@x402/axios`, to submit the actual payment. Product IDs should be discovered with `list_products` before calling product-specific tools. In mock mode, `place_order` simulates a successful order.

_Full upstream README: https://allmcps.com/mcp/-asterpay-mcp-server/readme_