Developer Tools

tracepay.ai

Tracks and traces stablecoin payment statuses across supported chains and providers.

1 endpoint3 known toolsFirst detected September 7, 2026Last detected September 7, 2026

ENDPOINT 1

https://tracepay.ai/mcp

No auth detected

MCP server metadata

Name: trace
Version: 1.0.0

Capabilities

tools

Known tools 3

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.

Potential side effects

get_trace

Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline.

Potential side effects

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).

Potential side effects

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.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.