Tracepay

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

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
77%
命名の品質
100%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~634トークン数(ツール定義)
~534 B一般的なレスポンスサイズ
注意への影響は最小限(128k コンテキストの 0.50%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "trace": {
      "url": "https://tracepay.ai/mcp"
    }
  }
}

リモートエンドポイント

https://tracepay.ai/mcpstreamable-http

できること

ツール一覧

ツール(3)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢trace_payment(input, input_type)

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.

入力スキーマ

{
  "type": "object",
  "properties": {
    "input": {
      "type": "string",
      "description": "Transaction hash, provider payment ID, or wallet address to trace."
    },
    "input_type": {
      "type": "string",
      "enum": [
        "auto",
        "base_tx_hash",
        "solana_signature",
        "bridge_transfer_id",
        "circle_payment_id",
        "base_address",
        "solana_address"
      ],
      "description": "Optional. Defaults to auto-detection."
    }
  },
  "required": [
    "input"
  ]
}
🟢get_trace(trace_id)

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

入力スキーマ

{
  "type": "object",
  "properties": {
    "trace_id": {
      "type": "string",
      "description": "Trace ID, e.g. \"tr_abc123\"."
    }
  },
  "required": [
    "trace_id"
  ]
}
🟢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.

入力スキーマ

{
  "type": "object",
  "properties": {}
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 3 件
検証済みバージョンは記録されていませんツール 3 件