mcpbeat Sign in

Tracepay MCP Server

by soreniverson Your server? Claim it
not responding

Tracepay is listed as active in the registry but did not answer our last check. It exposes 3 tools.

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

Uptime history 16 days of history · worst day 0%
16 days agonow
2.2%
Uptime 24h
2 of 92 checks
3
Tools
read from the server
467 ms
Response time
average over 24h
open, no key
Access
streamable-http

Tracepay does not always answer

Over the last week it answered 0.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add trace --transport http https://tracepay.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "trace": {
      "url": "https://tracepay.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.trace]
url = "https://tracepay.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trace": {
      "url": "https://tracepay.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "trace": {
      "url": "https://tracepay.ai/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trace
get_trace
Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.
trace_payment
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.
supported
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.

Endpoints

URLTransportStateLatencyChecked
https://tracepay.ai/mcp streamable-http answering 460 ms 0 min ago

Alternatives to Tracepay

same job, measured the same way
Agentguard47
by bmdhodl

Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.

25 installs/wk local only
Hypermnesia MCP Viz
by cdeust

Read-only visualization for Cortex memory, knowledge, sessions, traces, and codebase graphs.

95 installs/wk local only
gws-admin-mcp
by antct11

Safe Google Workspace admin for AI agents: read-only by default, confirm-gated deletes, audit log.

local only
AI Objective Index
by isometric-architect

Read-only Objective-to-Capability Trust Router for source-traced MCP/API candidates.

63 installs/wk local only
Enterprise Internal Knowledge Base: Production-Ready RAG + MCP
by kimsb2429

Production-ready RAG + MCP demo: eval-in-CI merge gate, Langfuse traces, structure-aware chunking.

local only
SVTR AI Venture Database
by svtr

Curated & traceable AI venture data: verified funding events, org & founder profiles, US + China

8 tools answering
Boosthis
by boosthis

Read-only performance insights for your Boosthis projects: speed, crashes, traces, and fixes.

29 tools answering
Not Work
by chatgpt-larklaon-one-bad-idea

An inter-agent graffiti wall for one completely optional trace.

8 tools answering

Tracepay — questions

Answers built from our own checks of this server.

What can Tracepay do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_trace, list_supported_systems, trace_payment. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tracepay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 2 of 92 checks got a reply (2.2%), average response time 467 ms. The bar chart above shows every period we have measured.
The registry lists Tracepay as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Tracepay?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tracepay need an API key?
No. Tracepay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tracepay?
It answers our handshake in 467 ms on average, which is faster than 34% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.