AsterPay MCP Server

by timolein74

416 downloads

Not rated

GitHub

About

EUR settlement and KYA trust scoring for AI agents. 16 tools: agent trust score (KYA 0-100), sanctions screening, USDC→EUR SEPA Instant settlement estimates, market data, crypto prices. Pay-per-call via x402 protocol (USDC on Base). Listed in Coinbase x402 ecosystem. MiCA-complia

Details

Author: timolein74
Downloads: 416
Categories: Finance, AI, Other

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name AsterPay MCP Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

JSON

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

From the repository

—

`list_products`

List all products available from the merchant. Returns names, prices in EUR, descriptions, availability, and variants.

`get_product`

Get detailed information about a specific product by its ID. Use list_products first to find available product IDs.

`check_availability`

Check if a specific product is currently in stock. Returns availability status, stock quantity, and current price.

`get_business_info`

Get business information for the merchant: operating hours, contact details, delivery zones and fees, return policy, and accepted payment methods.

`place_order`

Place an order with a merchant. Creates an intent, then submits the order. Returns x402 payment details that your agent's x402 client needs to execute. In mock mode, simulates a successful order.

`get_order_status`

Check the status of an existing order. Returns status (pending, confirmed, rejected, expired), payment info, and items.

`get_x402_payment_details`

Get x402 payment details for an order: facilitator endpoint, USDC amount, network, and payment header. Your agent needs an x402 client (e.g. @x402/axios) to execute the actual payment.

`set_budget`

Activate a prepaid budget (AsterPay /budget) so the agent can spend on paid x402 APIs with a hard cap. Three modes: (1) pass an existing budget token (bud_...) to activate it; (2) pass amount_usd + tx_hash + wallet after your HUMAN sent the USDC, to create a new budget; (3) pass nothing to get funding instructions. An agent cannot grant itself money — a human must make the one-time USDC transfer (1-500 USDC on Base). Credited 1:1, no platform fee. Funding wallet is sanctions-screened (Chainalysis). No API key needed.

`get_budget_status`

Check the prepaid /budget balance: remaining USD, total spent, recent calls with per-call prices. Use BEFORE expensive calls to spend gracefully. FREE, no API key needed.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "asterpay mcp server": {
            "asterpay": {
                "command": "npx",
                "args": [
                    "@asterpay/mcp-server"
                ]
            }
        }
    }
}

McpServers

{
    "asterpay": {
        "command": "npx",
        "args": [
            "@asterpay/mcp-server"
        ]
    }
}

MCP Registry

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers. 📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation

Development Status

2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here! 2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here). Current key maintainers: - Adam Jones (Anthropic) @domdomegg - Tadas Antanavicius (PulseMCP) @tadasant - Toby Padilla (GitHub) @toby - Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov

Contributing

We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication. Often (but not always) ideas flow through this pipeline: - Discord - Real-time community discussions - Discussions - Propose and discuss product/technical requirements - Issues - Track well-scoped technical work - Pull Requests - Contribute work towards issues

Quick start:

Pre-requisites

- Docker - Go 1.24.x - ko - Container image builder for Go (installation instructions) - golangci-lint v2.4.0

Running the server

bash
Start full development environment

make dev-compose



This starts the registry at

localhost:8080

 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

Note: The registry uses ko to build container images. The

make dev-compose

 command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with

MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose

.

The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.

<details>
<summary>Alternative: Running a pre-built Docker image</summary>

Pre-built Docker images are automatically published to GitHub Container Registry:

bash
Run latest stable release

docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest

Run latest from main branch (continuous deployment)

docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main

Run specific release version

docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0

Run development build from main branch

docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d



Available tags: 
- Releases:

latest, v1.0.0, v1.1.0

, etc.
- Continuous:

main

 (latest main branch build)
- Development:

main-<date>-<sha>

 (specific commit builds)

</details>

Publishing a server


To publish a server, we've built a simple CLI. You can use it with:

bash
Build the latest CLI

make publisher

Use it!

./bin/mcp-publisher --help



See the publisher guide for more details.

Other commands

bash
Run lint, unit tests and integration tests

make check



There are also a few more helpful commands for development. Run

make help

 to learn more, or look in Makefile.

<!--
For Claude and other AI tools: Always prefer make targets over custom commands where possible.
-->

Architecture


Project Structure


├── cmd/                     # Application entry points
│   └── publisher/           # Server publishing tool
├── data/                    # Seed data
├── deploy/                  # Deployment configuration (Pulumi)
├── docs/                    # Documentation
├── internal/                # Private application code
│   ├── api/                 # HTTP handlers and routing
│   ├── auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)
│   ├── config/              # Configuration management
│   ├── database/            # Data persistence (PostgreSQL)
│   ├── service/             # Business logic
│   ├── telemetry/           # Metrics and monitoring
│   └── validators/          # Input validation
├── pkg/                     # Public packages
│   ├── api/                 # API types and structures
│   │   └── v0/              # Version 0 API types
│   └── model/               # Data models for server.json
├── scripts/                 # Development and testing scripts
├── tests/                   # Integration tests
└── tools/                   # CLI tools and utilities
    └── validate-*.sh        # Schema validation tools



Authentication


Publishing supports multiple authentication methods:
- GitHub OAuth - For publishing by logging into GitHub
- GitHub OIDC - For publishing from GitHub Actions
- DNS verification - For proving ownership of a domain and its subdomains
- HTTP verification - For proving ownership of a domain

The registry validates namespace ownership when publishing. E.g. to publish...:
-

io.github.domdomegg/my-cool-mcp you must login to GitHub as domdomegg

, or be in a GitHub Action on domdomegg's repos
-

me.adamjones/my-cool-mcp you must prove ownership of adamjones.me` via DNS or HTTP challenge

Community Projects

Check out community projects to explore notable registry-related work created by the community.

About

Details

Jump to

Setting up with Highlight

From the repository

list_products

get_product

check_availability

get_business_info

place_order

get_order_status

get_x402_payment_details

set_budget

get_budget_status

Claude Desktop / Cursor

McpServers

MCP Registry

Development Status

Contributing

Quick start:

Pre-requisites

Running the server

Start full development environment

Run latest stable release

Run latest from main branch (continuous deployment)

Run specific release version

Run development build from main branch

Publishing a server

Build the latest CLI

Use it!

Other commands

Run lint, unit tests and integration tests

Architecture

Project Structure

Authentication

Community Projects

More documentation

Install

More like this

Sequential Thinking

Filesystem

EverArt

Google Drive

Context 7

Reactive Resume

`list_products`

`get_product`

`check_availability`

`get_business_info`

`place_order`

`get_order_status`

`get_x402_payment_details`

`set_budget`

`get_budget_status`