Tracepay is an MCP server published by io.github.soreniverson, hosted at tracepay.ai. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 3 tools, including trace_payment, get_trace, list_supported_systems.
Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed.
914 connections through 4 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs 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.
| Parameter |
|---|
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Type |
|---|
| Description |
|---|
| input * | string | Transaction hash, provider payment ID, or wallet address to trace. |
| input_type | string | Optional. Defaults to auto-detection. |
{
"name": "trace_payment",
"title": "Trace a payment",
"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": {
"type": "object",
"required": [
"input"
],
"properties": {
"input": {
"type": "string",
"description": "Transaction hash, provider payment ID, or wallet address to trace."
},
"input_type": {
"enum": [
"auto",
"base_tx_hash",
"solana_signature",
"bridge_transfer_id",
"circle_payment_id",
"base_address",
"solana_address"
],
"type": "string",
"description": "Optional. Defaults to auto-detection."
}
}
},
"annotations": {
"title": "Trace a payment",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.
| Parameter | Type | Description |
|---|---|---|
| trace_id * | string | Trace ID, e.g. "tr_abc123". |
{
"name": "get_trace",
"title": "Get an existing trace",
"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": {
"type": "object",
"required": [
"trace_id"
],
"properties": {
"trace_id": {
"type": "string",
"description": "Trace ID, e.g. \"tr_abc123\"."
}
}
},
"annotations": {
"title": "Get an existing trace",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}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.
No parameters.
{
"name": "list_supported_systems",
"title": "List supported payment systems",
"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": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "List supported payment systems",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.