Skip to content

Tracepay

by soreniverson · remote · no sign-in to list tools · v1.0.1 · published by GitHub user soreniverson

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

Final · 1
CompareRegistry entry

3 tools: 1 do something that can't be undone and 2 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http trace https://tracepay.ai/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • Warntrace_payment

    The server marks "trace_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "trace_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • Infolist_supported_systems

    The description mentions "credentials".

    Matched text

    description: "...Solana), providers requiring connected credentials (Bridge, Circle), and explicit capabili..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Can't be undone 1Claude Code: ask
  • trace_paymentUse 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 sho…1 finding

    Why it is in this group

    • The name "trace_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "trace_payment" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "trace_payment" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Trace a payment
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Claude Code: allow
  • get_traceRetrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline.No findings

    Why it is in this group

    • The name "get_trace" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.

    Annotations the server declares

    • title: Get an existing trace
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_supported_systemsList what Trace supports and can do: assets (USDC), chains with public tracing (Base, Solana), providers requiring connected credentials (Bridge, Circle), and explicit capability f…1 finding

    Why it is in this group

    • The name "list_supported_systems" says "list": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...Solana), providers requiring connected credentials (Bridge, Circle), and explicit capabili..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List supported payment systems
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http trace https://tracepay.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trace__get_trace",
      "mcp__trace__list_supported_systems"
    ],
    "ask": [
      "mcp__trace__trace_payment"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as trace. Review it before you use it.