All servers · Payments & accounting · Agent payments (x402) · Crypto & blockchain

Tracepay

io.github.soreniverson/trace · v1.0.1

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Read-only (all tools declare readOnlyHint)
Capabilities declared	tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100%

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

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

claude mcp add --transport http trace https://tracepay.ai/mcp

{
  "mcpServers": {
    "trace": {
      "url": "https://tracepay.ai/mcp"
    }
  }
}

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.

Website · JSON · Text for agents · Registry updated 2026-09-07