TrustAI MCP server

• Registry namecenter.trustai.pay/trustai-payverified in the MCP registry

The registry name sits under trustai.center. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools10
• Server calls itselftrustai-pay
• Server version1.2.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 120 ms.

• Its tools do none of the product's use cases we checked: mask sensitive data before it reaches an AI model; replace unsanctioned chatbot use with one approved workspace; identify AI usage that puts sensitive data at risk.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• What an agent can do with it0 of 3 use cases
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer198 ms
• Space in an agent's context≈ 1,335 tokensthe definitions of all its tools (12), which an agent carries on every turn
• Tool definitionsC · 69 of 100
• Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 10 of 12
• Not saying whether it only reads or can destroy: 12 of 12

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_models

  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.

• list_trending

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

• get_balance

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

• create_topup

  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).

• verify_topup

  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).

• claim_topup

  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…

• set_cap

  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.

• get_usage

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

• get_stats

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

• chat_completion

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