Tracepay

Name: Tracepay
Author: soreniverson

MCP serverMCP

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

by soreniversonhomepage ↗v1.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"trace","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability110/110 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	183 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
10 h ago	mcp initialize	ok	200	185 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
16 h ago	mcp initialize	ok	200	147 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
22 h ago	mcp initialize	ok	200	158 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
28 h ago	mcp initialize	ok	200	162 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
35 h ago	mcp initialize	ok	200	146 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	278 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	395 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	603 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	149 ms	server trace 1.0.0 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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 nex
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 e

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.soreniverson/trace

first seen 1 mo ago · fetched 2 d agoopen ↗

Field history (8 recent events)

1 mo ago · declared · name → "Tracepay"
1 mo ago · declared · version → "1.0.1"
1 mo ago · declared · publisherName → "soreniverson"
1 mo ago · declared · homepageUrl → "https://tracepay.ai"
1 mo ago · declared · summary → "Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed."
1 mo ago · declared · protocols → ["mcp"]
1 mo ago · declared · version → "1.0.0"
1 mo ago · declared · description → "Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed."

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from