Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

claude mcp add --transport http trace https://tracepay.ai/mcp

[mcp_servers.trace]
url = "https://tracepay.ai/mcp"

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

{
  "mcpServers": {
    "trace": {
      "type": "http",
      "url": "https://tracepay.ai/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=trace&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdHJhY2VwYXkuYWkvbWNwIn0%3D"
}

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

{
  "mcpServers": {
    "trace": {
      "httpUrl": "https://tracepay.ai/mcp"
    }
  }
}

extensions:
  "trace":
    enabled: true
    name: "trace"
    type: streamable_http
    uri: "https://tracepay.ai/mcp"
    timeout: 300

Quality 88 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene93 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations3 of 3 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 701 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 701 tokens to load them all · tool set dd4b851bfbb5 · checked 2026-10-20 09:31 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 77 / 100

no-repository

provenance45

liveness100

freshness85

hygiene80

+website +reachable +uptime-100% ~updated-43d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://tracepay.ai/mcp` streamable-http	none	yes	100%	260 ms	2025-11-25	2026-10-20

Tools (3)

`get_trace`read-only	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`read-only	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.
`trace_payment`read-only	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.github.soreniverson/trace",
  "icons": [
    {
      "src": "https://tracepay.ai/trace-icon.png",
      "sizes": [
        "512x512"
      ],
      "mimeType": "image/png"
    }
  ],
  "title": "Tracepay",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://tracepay.ai/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "websiteUrl": "https://tracepay.ai",
  "description": "Read-only payment state for USDC on Base/Solana (Bridge, Circle): completed, failed, or delayed."
}