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.
Available components
Last scanned (9 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 992 tokens (~82/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 828 → 992 ▼ functional
- Tool coverage: 12% → 23% ▲ functional
- Server version: 1.4.0 → 1.5.0 functional
- New tool “list_price_changes” functional
- 2 Nov 26 +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.
- 30 Oct 26 +1
- Server version: 1.3.0 → 1.4.0 functional
- 29 Oct 26 0
- Schema quality: 748 → 828 ▼ functional
- Server version: 1.2.0 → 1.3.0 functional
- New tool “quote” functional
- 28 Oct 26 +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.
- 27 Oct 26 0
- Tool “list_trending” rewrote its description, which is the text the model reads security
- Server version: 1.1.0 → 1.2.0 functional
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://pay.trustai.center/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.trustai.center | CN=YR1,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | RSA 2048 | SHA256-RSA | 60eb1f6c7b99adceaaa5b00dbec85d55d35 |
| SANs: *.trustai.center | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pay.trustai.center. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| center. | present | 50192 | 8 | Verified |
| trustai.center. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pay.trustai.center/mcp | Verified | 200 | |
| http (plaintext) | http://pay.trustai.center/mcp | HTTPS enforced | 308 | https://pay.trustai.center/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chat_completion ~51
Run a chat completion billed to a tai_ key's credits.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| max_tokens | number | – | – |
| messages | array | yes | – |
| model | string | yes | – |
No output schema declared.
No examples provided.
claim_topup ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| chain | string | yes | – |
| signature | string | – | – |
| tx_hash | string | yes | – |
No output schema declared.
No examples provided.
create_topup ~80
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).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| chain | string | – | – |
| pack | number | yes | Credits in USD (1 = starter pack) |
| promo | string | – | – |
No output schema declared.
No examples provided.
get_balance ~46
Get the credit balance, spend cap and amount spent for a tai_ API key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | tai_ key (optional if sent as Authorization: Bearer header) |
No output schema declared.
No examples provided.
get_stats ~35
Public platform stats from our database (tokens and requests in the last 24h, keys created, top models). Real numbers only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage ~55
Usage and audit log for a tai_ key: recent charges (model, tokens, cost), top-ups, last-24h totals, balance and limits.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
list_models ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
list_price_changes ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
list_trending ~40
Featured trending models with prices (ranked by recent tokens served when available, otherwise a curated ranking; see ranking field).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
quote ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input_tokens | number | – | – |
| max_tokens | number | – | – |
| messages | array | – | – |
| model | string | yes | – |
No output schema declared.
No examples provided.
set_cap ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| daily_limit_usd | number|null | – | – |
| per_request_max_usd | number|null | – | – |
| spend_cap_usd | number|null | – | – |
No output schema declared.
No examples provided.
verify_topup ~75
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).
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| signature | string | – | – |
| tx_hash | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · pay.trustai.center
claude mcp add --transport http center-trustai-pay-trustai-pay 'https://pay.trustai.center/mcp'
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.