NestDaddy

Tracepay

io.github.soreniverson/trace · v1.0.1

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

Connect Remote server

Terminal
claude mcp add --transport http trace https://tracepay.ai/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "trace": {
      "url": "https://tracepay.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "trace": {
      "type": "http",
      "url": "https://tracepay.ai/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://tracepay.ai/mcp

Tools 3 found in our last check

  • 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…

  • 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…

Details

Endpointhttps://tracepay.ai/mcp (Streamable HTTP)
First published7 Sep 2026
Last updated7 Sep 2026
Registry nameio.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.