# trustai.center pay (remote · pay.trustai.center)

Pay-per-use LLM inference for agents: pay in USDC/USDT or per call via x402. 247 chat models.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `pay.trustai.center`: 68/100 (this document), [markdown](https://verifymcp.io/servers/center-trustai-pay-trustai-pay/pay.md), [page](https://verifymcp.io/servers/center-trustai-pay-trustai-pay/pay)

## Channel facts

- Endpoint: `https://pay.trustai.center/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 992 tokens (~82/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 23% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 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 trustai.center pay MCP server?

trustai.center pay is a hosted endpoint at https://pay.trustai.center/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 center-trustai-pay-trustai-pay 'https://pay.trustai.center/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "center-trustai-pay-trustai-pay": {
      "url": "https://pay.trustai.center/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "center-trustai-pay-trustai-pay": {
      "type": "http",
      "url": "https://pay.trustai.center/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.center-trustai-pay-trustai-pay]
url = "https://pay.trustai.center/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "center-trustai-pay-trustai-pay": {
      "type": "remote",
      "url": "https://pay.trustai.center/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add center-trustai-pay-trustai-pay --url 'https://pay.trustai.center/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  center-trustai-pay-trustai-pay:
    url: "https://pay.trustai.center/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "center-trustai-pay-trustai-pay": {
      "Transport": "http",
      "Url": "https://pay.trustai.center/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add center-trustai-pay-trustai-pay -t streamable-http -u 'https://pay.trustai.center/mcp'
```

### Other

```json
{
  "mcpServers": {
    "center-trustai-pay-trustai-pay": {
      "type": "http",
      "url": "https://pay.trustai.center/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-11-05 (score 68, +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-11-03 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 828 → 992
- [functional improvement] Tool coverage: 12% → 23%
- [functional] Server version: 1.4.0 → 1.5.0
- [functional] New tool “list_price_changes”

### 2026-11-02 (score 66, +1)

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

### 2026-10-30 (score 65, +1)

- [functional] Server version: 1.3.0 → 1.4.0

### 2026-10-29 (score 64, 0)

- [functional regression] Schema quality: 748 → 828
- [functional] Server version: 1.2.0 → 1.3.0
- [functional] New tool “quote”

### 2026-10-28 (score 64, +1)

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

### 2026-10-27 (score 63, 0)

- [security] Tool “list_trending” rewrote its description, which is the text the model reads
- [functional] Server version: 1.1.0 → 1.2.0

### 2026-10-26 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (12)

### `list_models` (~132 tokens)

List servable text chat models with USD prices (pricing.vs_list vs maker list price). Pass include=discovery to also see image/video models (servable:false). Filter by modality, max output price, text search; sort by popularity or price.

Input parameters:

- `include` (string): Also list image/video/other models that are not servable here (servable:false)
- `limit` (number)
- `max_price` (number): Max USD per 1M output tokens (or per unit for media)
- `modality` (string)
- `q` (string)
- `sort` (string)

### `list_trending` (~40 tokens)

Featured trending models with prices (ranked by recent tokens served when available, otherwise a curated ranking; see ranking field).

Input parameters:

- `limit` (number)

### `quote` (~80 tokens)

Price check before paying: worst-case USD cost and exact x402 amount for a model + max_tokens (+ optional messages or input_tokens), with up to 3 cheaper trending alternatives. No key needed, never charges.

Input parameters:

- `input_tokens` (number)
- `max_tokens` (number)
- `messages` (array)
- `model` (string, required)

### `list_price_changes` (~154 tokens)

Price-change feed: models whose price went down/up, or that were added/removed, since a date (default last 7 days), diffed between daily catalog syncs. Use type=price_down to find models that just got cheaper. No key needed.

Input parameters:

- `days` (number): 1-90
- `limit` (number)
- `modality` (string)
- `q` (string): substring of model id
- `servable` (boolean): only models callable now via chat completions
- `since` (string): ISO date or date-time (default: now - days)
- `type` (string): comma-separated: price_down, price_up, price_changed, added, removed

### `get_balance` (~46 tokens)

Get the credit balance, spend cap and amount spent for a tai_ API key.

Input parameters:

- `api_key` (string): tai_ key (optional if sent as Authorization: Bearer header)

### `create_topup` (~80 tokens)

Create a stablecoin top-up order. Returns the deposit address, chain and the exact amount to send. Omit api_key to create a new key (returned once).

Input parameters:

- `api_key` (string)
- `chain` (string)
- `pack` (number, required): Credits in USD (1 = starter pack)
- `promo` (string)

### `verify_topup` (~75 tokens)

Confirm a top-up after sending funds, by order id and transaction hash/signature. Credits the amount received (tolerance -0.5% or $0.01; other amounts need the sender's signature).

Input parameters:

- `order_id` (string, required)
- `signature` (string)
- `tx_hash` (string, required)

### `claim_topup` (~99 tokens)

Credit a stablecoin transfer to our address that has no matching order (or a non-exact amount). Requires the sending wallet's signature of 'trustai.center claim <chain>:<tx_hash>'. Max 7 days old, each tx once. Omit api_key to get a new key.

Input parameters:

- `api_key` (string)
- `chain` (string, required)
- `signature` (string)
- `tx_hash` (string, required)

### `set_cap` (~91 tokens)

Set spend controls on a tai_ key: total spend cap, daily limit (UTC day) and per-request max, in USD. Omit a field to keep it, pass null to remove it.

Input parameters:

- `api_key` (string)
- `daily_limit_usd` (number|null)
- `per_request_max_usd` (number|null)
- `spend_cap_usd` (number|null)

### `get_usage` (~55 tokens)

Usage and audit log for a tai_ key: recent charges (model, tokens, cost), top-ups, last-24h totals, balance and limits.

Input parameters:

- `api_key` (string)
- `limit` (number)

### `get_stats` (~35 tokens)

Public platform stats from our database (tokens and requests in the last 24h, keys created, top models). Real numbers only.

### `chat_completion` (~51 tokens)

Run a chat completion billed to a tai_ key's credits.

Input parameters:

- `api_key` (string)
- `max_tokens` (number)
- `messages` (array, required)
- `model` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 68
- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 66
- 2026-11-01: 65
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 64
- 2026-10-28: 64
- 2026-10-27: 63
- 2026-10-26: 63
- 2026-10-25: 62

## Common questions

### What is the trustai.center pay MCP server?

trustai.center pay is an MCP server listed in the public MCP registry as center.trustai.pay/trustai-pay. Pay-per-use LLM inference for agents: pay in USDC/USDT or per call via x402. 247 chat models. This page covers its hosted endpoint (https://pay.trustai.center/mcp).

### Is the trustai.center pay MCP server safe to use?

trustai.center pay scores 68 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 trustai.center pay MCP server expose?

trustai.center pay exposes 12 tools: list_models, list_trending, quote, list_price_changes, get_balance, and 7 more. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.

### Does the trustai.center pay MCP server require authentication?

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

### Is the trustai.center pay MCP server still maintained?

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

### What did VerifyMCP test on the trustai.center pay MCP server?

VerifyMCP ran 12 checks on trustai.center pay, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about trustai.center pay: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pay.trustai.center/mcp
- Website: https://pay.trustai.center/docs
- Changelog RSS feed: https://verifymcp.io/servers/center-trustai-pay-trustai-pay/pay.xml
- Changelog JSON feed: https://verifymcp.io/servers/center-trustai-pay-trustai-pay/pay/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/center-trustai-pay-trustai-pay/pay.json
- HTML version of this page: https://verifymcp.io/servers/center-trustai-pay-trustai-pay/pay