AsterPay — EUR Settlement For AI Agents MCP Server

EUR settlement + trust for AI agent commerce: budgets, KYA, merchant discovery. 22 tools. Exposed over MCP by the asterpay — eur settlement for ai agents mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This hook implements the IACPHook interface to enforce AsterPay's 5-layer Trust Framework before AI agents can participate in ERC-8183 commerce jobs.

Its toolset

Everything the assistant can do here goes through one of these:

• Contract — Purpose
• AsterPayKYAHook.sol — Main hook — sanctions + trust score gate
• IACPHook.sol — ERC-8183 hook interface
• IAgenticCommerce.sol — Read-only ACP job interface
• IAgentTrustScore.sol — AsterPay trust score oracle interface
• ISanctionsOracle.sol — Chainalysis oracle interface
• minTrustScore — 20
• maxScoreAge — 3600
• sanctionsEnabled — true
• Event — When
• KYAVerified — Agent passes all checks
• KYABlocked — Agent fails any check

Configuration

You will need one environment variable: PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. AsterPay — EUR Settlement For AI Agents's toolset — Contract, AsterPayKYAHook.sol, IACPHook.sol and 11 more — is a fair guide to whether it matches your workflow. It is maintained by io.asterpay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against AsterPay — EUR Settlement For AI Agents's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch AsterPay — EUR Settlement For AI Agents.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the asterpay — eur settlement for ai agents mcp server does with a few real requests.