AsterPay — EUR Settlement & Agent Trust API
Description
EUR settlement layer for AI agents. Convert USDC/EURC to EUR via SEPA Instant. **Free tools (no payment required):** - `check_agent_trust` — KYA trust score 0-100 for any Ethereum wallet - `get_trust_tier` — Trust tier classification (open/verified/trusted/enterprise) - `get_settlement_estimate` — Calculate EUR amount for USDC conversion - `discover_services` — List all available AsterPay API endpoints **Protocols:** x402, A2A, ERC-8004 **Chains:** Base, Ethereum, Solana, XRPL, Polygon, BNB Chain **Docs:** https://asterpay.io/docs
What our measurements say
AsterPay — EUR Settlement & Agent Trust API is a remote MCP server published at api.asterpay.io. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 602 ms, a delay an agent will notice. It exposes a broad tool surface of 20 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Most tool names directly indicate their purpose (e.g., 'check_agent_trust', 'settlement_estimate')
- Free tools are explicitly labeled with 'FREE' in descriptions
- Some tools include cost details and usage constraints (e.g., 'ai_fact_check' specifies source-bounded analysis)
Weaknesses
- Multiple tools with similar purposes (e.g., 'get_agent_tier' vs 'get_trust_tier')
- Descriptions often focus on 'what' the tool does rather than 'when' to use it
- No explicit error handling or parameter constraints in descriptions
- Ambiguous tool names (e.g., 'data_get' lacks specificity compared to 'data_catalog')
check_agent_trust— Overlaps with 'verify_agent_identity' in trust verification scopeget_agent_tier— Functionally similar to 'get_trust_tier' with unclear differentiationsettlement_estimate— Redundant with 'get_settlement_estimate' (same name in tool list)data_get— Vague name with no clear purpose compared to 'data_catalog'ai_fact_check— No explicit error handling for invalid source inputs
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — Era changed from auth-gated to legacy · Agent trust status updated to legacy mode
- 2026-09-11T05:44:28.819Z — Compliance score set to 100 · Indicates full compliance with regulations
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 198ms → warm 218ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.1
- Supported versions: — → 2024-11-05
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/asterpay-mcp-server)<a href="https://mcpmetrics.io/servers/asterpay-mcp-server"><img src="https://mcpmetrics.io/badge/asterpay/mcp-server/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see