AsterPay — EUR Settlement for AI Agents MCP server
io.asterpay/asterpayasterpay.iostreamable-httpv2.1.0Scanned
EUR settlement + trust for AI agent commerce: budgets, KYA, merchant discovery. 22 tools.
4 tools: 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the AsterPay — EUR Settlement for AI Agents MCP server can do
The AsterPay — EUR Settlement for AI Agents MCP server is published by asterpay.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: check_agent_trust and settlement_estimate), but cannot delete data. 2 tools only read.
4 tools bring in text other people can write (check_agent_trust, settlement_estimate, market_rates and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Oct 30, 2026, version 2.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
check_agent_trustKnow Your Agent (KYA): score how trustworthy an AI agent or wallet is before paying or transacting with it.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, wallet age/activity). Input: an Ethereum address. Free, read-only.
Annotations the server declares
- title: KYA Trust Score
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
settlement_estimateEstimate converting a USDC amount to EUR via AsterPay's EUR off-ramp.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: USDC→EUR Settlement Estimate
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
market_ratesGet current reference market rates used by AsterPay (e.g.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get current reference market rates used by AsterPay (e.g. USDC, EURC, major crypto rates and FX). No input. Free, read-only.
Annotations the server declares
- title: Crypto Market Rates
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
merchant_resolveResolve a European business to its verified payment endpoint (IBAN/BIC) via AsterPay's Merchant Payment Endpoint (MPE), from provable sources only.Reads text others writeNo findings
Why it is in this group
- The name "merchant_resolve" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, y_tunnus, company_number, lei, duns). Tip: business_id_type 'demo' (or business_id 'FI-DEMO-0001') returns a safe demo merchant. Free, read-only — resolution does not move money.
Annotations the server declares
- title: Resolve Merchant Payment Endpoint
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:55 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp-api.asterpay.io/mcp: tools/list returned 4 tools to an anonymous client, including check_agent_trust (write), settlement_estimate (write)
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 404 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 404 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 2 (and 1 more).View diff
- HTTP status of an anonymous initialize: 404 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 2.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http asterpay https://mcp-api.asterpay.io/mcpclaude mcp add --transport http asterpay https://mcp-api.asterpay.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__asterpay__market_rates",
"mcp__asterpay__merchant_resolve"
],
"ask": [
"mcp__asterpay__check_agent_trust",
"mcp__asterpay__settlement_estimate"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as asterpay. Review it before you use it.
Capability tags behind 4 rules
- mcp__asterpay__check_agent_trust untrusted-input
- mcp__asterpay__settlement_estimate untrusted-input
- mcp__asterpay__market_rates untrusted-input
- mcp__asterpay__merchant_resolve untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.asterpay/asterpay/verify?hash=df916e7b02467429e0e2e03a7d0b2176556ddb16fce450976a69bbcc1d7617af" | jq -e '.changed == false'Pinned hash df916e7b0246, from Oct 30, 2026, 00:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.asterpay/asterpay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.asterpay/asterpay)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:13 UTC.
AsterPay — EUR Settlement for AI Agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AsterPay — EUR Settlement for AI Agents MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AsterPay — EUR Settlement for AI Agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AsterPay — EUR Settlement for AI Agents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the AsterPay — EUR Settlement for AI Agents MCP server have?
- 4 tools: 2 write, 2 read. check_agent_trust, settlement_estimate, market_rates and merchant_resolve.
Does the AsterPay — EUR Settlement for AI Agents MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AsterPay — EUR Settlement for AI Agents MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AsterPay — EUR Settlement for AI Agents MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 30, 2026.