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개