Connect-MCP

Tracepay

io.github.soreniverson/trace · v1.0.1

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

MCPremoteno credentialsFinanceCrypto

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 3 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 3 tools · 3 read, 0 write · Finance, Crypto, Developer tools

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://tracepay.ai/mcp

Tools

3 tools listed at last check
  • 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. Typical triggers: 'the recipient says the payment never arrived', 'this payout is stuck', 'did this tra
  • 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; cannot send, retry, or sign). Call this when unsure whether a payment is in scope for trace_payment.

Badge

Connect-MCP badge for io.github.soreniverson/trace

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.soreniverson/trace.svg)](https://clawy.uk/mcp/s/io.github.soreniverson/trace)