Tracepay
Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"trace": {
"url": "https://tracepay.ai/mcp"
}
}
}Remote endpoints
https://tracepay.ai/mcpstreamable-httpWhat it can do
Tool inventory
Tools (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.
Input Schema
{
"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.
Input Schema
{
"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.
Input Schema
{
"type": "object",
"properties": {}
}Community
Evidence