INDIVIDUAL MCP TOOL

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.

tracepay.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://tracepay.ai/mcp

No auth detected

Connect to this endpoint to inspect the live schema for trace_payment and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description suggests a financial action.

Parent server

tracepay.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.trace]
url = "https://tracepay.ai/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: trace
Remote MCP URL: https://tracepay.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "trace": {
      "type": "http",
      "url": "https://tracepay.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "trace",
  "transport": "streamable-http",
  "url": "https://tracepay.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

get_trace — Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline.
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).