Skip to content
AsterPay logo

AsterPay MCP server

Which servers in the official MCP registry are AsterPay's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to AsterPay

Whose server it is
  • Registry nameio.asterpay/asterpayverified in the MCP registry

The registry name sits under asterpay.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-15
  • Stateanswerschecked 2026-10-15
  • Tools4
  • Server calls itselfasterpay
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 106 ms.

Tools it offers4 tools · read 2026-10-15
  • check_agent_trust

    Know Your Agent (KYA): score how trustworthy an AI agent or wallet is before paying or transacting with it. Returns a trust score 0-100, tier (Open/Verified/Trusted/Enterprise) and components (ERC-8004 identity, sanctions screening…

  • settlement_estimate

    Estimate converting a USDC amount to EUR via AsterPay's EUR off-ramp. Returns the exchange rate, AsterPay fee (0.5% + €0.10 on the EU rail), net EUR amount and SEPA Instant timing. Input: a USDC amount. Free, read-only — no payment is made.

  • market_rates

    Get current reference market rates used by AsterPay (e.g. USDC, EURC, major crypto rates and FX). No input. Free, read-only.

  • merchant_resolve

    Resolve a European business to its verified payment endpoint (IBAN/BIC) via AsterPay's Merchant Payment Endpoint (MPE), from provable sources only. Provide EITHER a merchant_id OR a business_id together with its business_id_type (vat…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "asterpay": {
      "type": "http",
      "url": "https://mcp-api.asterpay.io/mcp"
    }
  }
}

OpenAPI spec

66 paths, read 2026-10-15. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.