Tracepay

io.github.soreniversonPublished by GitHub account soreniversonv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Lets an assistant check the read-only status of USDC payments on Base and Solana, including completed, failed, or delayed states.

What you can do
Tracepay is a remote MCP server that exposes read-only payment state for USDC transfers on Base and Solana, referencing Bridge and Circle. It reports whether a payment is completed, failed, or delayed. No tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs to confirm the outcome of a USDC payment on Base or Solana, for example to check whether a transfer settled, failed, or is still pending. It is a status lookup, not a way to move funds.
Requirements
A remote MCP endpoint at over streamable HTTP. No packages, environment variables, headers, or authentication are declared in the manifest.
Before you install
The server is described as read-only for payment state, but the manifest declares no authentication, so consider what payment identifiers you send to a third-party endpoint. No credentials, keys, or spending actions are shown in the input.

Installation

In SourceWeft

  1. Open Tracepay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.soreniverson%2Ftrace/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

3

trace_payment

Trace a 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 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.

Parametersinputrequiredinput_type

get_trace

Get an existing trace

Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.

Parameterstrace_idrequired

list_supported_systems

List supported payment 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.

Takes no parameters.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.