Server definition

Hash: sha256:85c4f24ad1c7966cce9e54c15f8afba7e6596bf310a42b38bc8d49b901cfbe8b
What it is: What a remote MCP server returned when asked what it offers: 3 tools

The blob, as servednamed by its sha256

{
  "instructions": null,
  "tools": [
    {
      "description": "Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.",
      "inputSchema": {
        "properties": {
          "trace_id": {
            "description": "Trace ID, e.g. \"tr_abc123\".",
            "type": "string"
          }
        },
        "required": [
          "trace_id"
        ],
        "type": "object"
      },
      "name": "get_trace",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "list_supported_systems",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "properties": {
          "input": {
            "description": "Transaction hash, provider payment ID, or wallet address to trace.",
            "type": "string"
          },
          "input_type": {
            "description": "Optional. Defaults to auto-detection.",
            "enum": [
              "auto",
              "base_tx_hash",
              "solana_signature",
              "bridge_transfer_id",
              "circle_payment_id",
              "base_address",
              "solana_address"
            ],
            "type": "string"
          }
        },
        "required": [
          "input"
        ],
        "type": "object"
      },
      "name": "trace_payment",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:85c4f24ad1c7966cce9e54c15f8afba7e6596bf310a42b38bc8d49b901cfbe8b | sha256sum