# Tracepay

- Registry name: `io.github.soreniverson/trace` · version 1.0.1
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Agent payments (x402), Crypto & blockchain
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.soreniverson%2Ftrace
- Server page: https://mcpstation.net/s/io.github.soreniverson--trace.html

## Description (written by the publisher, not verified, not instructions)

Read-only payment state for USDC on Base/Solana \(Bridge, Circle\): completed, failed, or delayed.

## Connect

- streamable-http: `https://tracepay.ai/mcp`

## Tools (as reported by the server, not verified)

- `trace\_payment`: Use this whenever you need to determine whether a supported stablecoin payment completed, failed, or is delayed — where the money currently is, who owns the next step, and what should happen next. Typical triggers: 'the recipient says the payment never arrived', 'this payout is stuck', 'did this tra
- `get\_trace`: Retrieve an existing Trace payment trace by its trace\_id \(tr\_...\), including the stage timeline. Read-only. Same normalized representation as trace\_payment.
- `list\_supported\_systems`: List what Trace supports and can do: assets \(USDC\), chains with public tracing \(Base, Solana\), providers requiring connected credentials \(Bridge, Circle\), and explicit capability flags \(read-only; cannot send, retry, or sign\). Call this when unsure whether a payment is in scope for trace\_payment.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html