# Soreniverson Trace MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.soreniverson%2Ftrace
Registry id: `mcp-registry/io.github.soreniverson/trace`
Status: live (checked 2026-10-27T03:24:21.861Z)

## Verdict

Soreniverson Trace MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 717 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (96/100) across 3 tools, costing an agent about 463 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 717 ms | 34% of MCP servers |
| p95 handshake latency | 2829 ms | — |
| Checks in 30 days | 4,946 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 3 | — |
| Tool-list size for an agent | ~463 tokens | 90% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "soreniverson-trace-mcp-server": {
      "type": "http",
      "url": "https://tracepay.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http soreniverson-trace-mcp-server https://tracepay.ai/mcp
```

## Tools (3)

- `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.
- `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 e
- `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 nex

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.