What are the risks of connecting to tracepay.ai?

No blocking issues were found in the static + spec checks. Overall trust grade B (84/100).

When was tracepay.ai last audited?

Last checked 2026-10-12; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

tracepay.ai

Item: tracepay.ai
Rating: 84
Author: wmcp.sh

https://tracepay.ai/mcp

84/100 · MCP Trust Grade · checked 17d ago · MCP 2025-06-18

Is the tracepay.ai MCP server safe to use?

Independent trust grade B (84/100). No blocking issues found in the static + spec checks. wmcp.sh continuously watches tracepay.ai for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

✓ Watched since 2026-10-12 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 3 tools · Finance & Crypto

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 ow

get_trace

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

list_supported_systems

List what Trace supports and can do: assets (USDC), chains with public tracing (Base, Solana), providers requiring connected credentials (Bridge, Circ

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 3 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

3 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 2399ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%60

67% of tools have typed inputSchema
0/3 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade tracepay.ai on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Run tracepay.ai? Claim it (free) to get drift alerts and show an independently-verified trust badge. The grade stays free — claiming just ties it to you.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — tracepay.ai grade B

Share on X Open card image

https://wmcp.sh/mcp/grade/tracepay.ai

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B](https://wmcp.sh/mcp/grade/tracepay.ai/badge.svg)](https://wmcp.sh/mcp/grade/tracepay.ai)

HTML

<a href="https://wmcp.sh/mcp/grade/tracepay.ai"><img src="https://wmcp.sh/mcp/grade/tracepay.ai/badge.svg" alt="MCP Trust Grade B · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.