Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed.
Connect Remote server
claude mcp add --transport http trace https://tracepay.ai/mcp
{
"mcpServers": {
"trace": {
"url": "https://tracepay.ai/mcp"
}
}
}
{
"servers": {
"trace": {
"type": "http",
"url": "https://tracepay.ai/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://tracepay.ai/mcp
Tools 3 found in our last check
trace_paymentUse 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…
get_traceRetrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.
list_supported_systemsList 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…
Details
| Endpoint | https://tracepay.ai/mcp (Streamable HTTP) |
| First published | 7 Sep 2026 |
| Last updated | 7 Sep 2026 |
| Registry name | io.github.soreniverson/trace |
More finance and crypto servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
