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.
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
claude mcp add trace --transport http https://tracepay.ai/mcp
https://tracepay.ai/mcp
[mcp_servers.trace]
url = "https://tracepay.ai/mcp"
{
"mcpServers": {
"trace": {
"url": "https://tracepay.ai/mcp"
}
}
}
{
"servers": {
"trace": {
"type": "http",
"url": "https://tracepay.ai/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_trace
trace_payment
list_supported_systems
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://tracepay.ai/mcp | streamable-http | answering | 100 ms | 13 min ago |
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
UETR tracking and SWIFT payment tracking for AI apps. Read transfer status and manage monitoring.
Read-only Petra Security MCP: M365 compromise incidents, failed attacks, posture, tenants, usage.
Read-only visualization for Cortex memory, knowledge, sessions, traces, and codebase graphs.
Safe Google Workspace admin for AI agents: read-only by default, confirm-gated deletes, audit log.
Instagram research, Story monitoring and creator comparison. MCP x402 paid calls, USDC on Solana.
Create, read and delete shipments; read track and trace and pickup points in MyParcel.
Your own assistant uses the same validated, read-only queries as TraceLog.
Answers built from our own checks of this server.