# Tracepay (remote · tracepay.ai)

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

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- remote · `tracepay.ai`: 82/100 (this document), [markdown](https://verifymcp.io/servers/soreniverson-trace/tracepay.md), [page](https://verifymcp.io/servers/soreniverson-trace/tracepay)

## Channel facts

- Endpoint: `https://tracepay.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 437 tokens (~145/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tracepay MCP server?

Tracepay is a hosted endpoint at https://tracepay.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http soreniverson-trace 'https://tracepay.ai/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.soreniverson-trace]
url = "https://tracepay.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "soreniverson-trace": {
      "type": "remote",
      "url": "https://tracepay.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add soreniverson-trace --url 'https://tracepay.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  soreniverson-trace:
    url: "https://tracepay.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "soreniverson-trace": {
      "Transport": "http",
      "Url": "https://tracepay.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add soreniverson-trace -t streamable-http -u 'https://tracepay.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `trace_payment` (~309 tokens)

Trace a 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.

Input parameters:

- `input` (string, required): Transaction hash, provider payment ID, or wallet address to trace.
- `input_type` (string): Optional. Defaults to auto-detection.

### `get_trace` (~56 tokens)

Get an existing trace

Retrieve an existing Trace payment trace by its trace_id (tr_...), including the stage timeline. Read-only. Same normalized representation as trace_payment.

Input parameters:

- `trace_id` (string, required): Trace ID, e.g. "tr_abc123".

### `list_supported_systems` (~72 tokens)

List supported payment 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/soreniverson-trace/tracepay#diagnostics

## Score history

- 2026-09-22: 82
- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 75
- 2026-09-06: 75

## Common questions

### What is the Tracepay MCP server?

Tracepay is an MCP server listed in the public MCP registry as io.github.soreniverson/trace. Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed. This page covers its hosted endpoint (https://tracepay.ai/mcp).

### Is the Tracepay MCP server safe to use?

Tracepay scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Tracepay MCP server expose?

Tracepay exposes 3 tools: trace_payment, get_trace, list_supported_systems. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.

### Does the Tracepay MCP server require authentication?

No. We connected to Tracepay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tracepay MCP server still maintained?

Tracepay is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://tracepay.ai/mcp
- Website: https://tracepay.ai/
- Changelog RSS feed: https://verifymcp.io/servers/soreniverson-trace/tracepay.xml
- Changelog JSON feed: https://verifymcp.io/servers/soreniverson-trace/tracepay.json
- HTML version of this page: https://verifymcp.io/servers/soreniverson-trace/tracepay