Tracepay MCP server

• get_traceFree

  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_systemsFree

  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.

• trace_paymentFree

  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 transaction go through?'. Give it a Base transaction hash, Solana signature, Bridge transfer ID, Circle payment ID, or a Base/Solana wallet address (USDC). Trace correlates blockchain and provider evidence into one deterministic normalized state: completed/terminal flags, health, current stage and owner, an evidence-backed diagnosis code with a machine-readable suggested action and retry timing, and a knowledge model separating observed facts from inferences from what Trace cannot see (e.g. beneficiary bank credit — onchain finality never proves the recipient's bank credited funds; unknown never means failed). Public blockchain data works without authentication; provider-connected state requires an API key. If the user has no identifier, ask for a transaction hash, provider payment ID, or supported wallet address. Read-only: this tool never moves funds, retries payments, signs transactions, or guarantees beneficiary receipt — do not use it to send or swap anything. If a payment's state is unresolved, do NOT send a replacement payment; follow the returned warnings and suggested action instead.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1307ms20/20
• Tool poisoning3 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

Tracepay: common questions

Is Tracepay MCP server safe?

With care: it is graded C, so read the findings first (67/100). Read the Tracepay safety report

How do I install Tracepay?

It runs remotely at tracepay.ai. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Tracepay need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Tracepay maintained?

The latest release is v1.0.1.

Is Tracepay up?

100% of our last 5 checks got an answer. We check remote servers about four times a day.

What can I use instead of Tracepay?

Servers from other publishers that do the same job: Eqvps MCP server, x402 Seller MCP server and Anyway Possible Paid Agent Utilities MCP server. Compare all Tracepay alternatives.