← All launches
0 Report

Trace

by @fastdrop

MCP Verified 7 days ago Registry import free

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

Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed. Official MCP Registry: io.github.soreniverson/trace@1.0.0. Remote endpoint: https://tracepay.ai/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.soreniverson/trace and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 6 Sept 2026. Not supplied by the maker.

  • 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. Typ

  • 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; can

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.