Skip to content

trustai.center pay MCP server

center.trustai.pay/trustai-paypay.trustai.centerstreamable-httpv1.0.0Scanned

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

12 tools: 3 do something that can't be undone, 3 change things and 6 only read.

Tools: 0 delete, 3 irreversible, 3 write, 6 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the trustai.center pay MCP server can do

The trustai.center pay MCP server is published by pay.trustai.center, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_topup, verify_topup and claim_topup) and create or change data (3 tools: quote, set_cap and chat_completion), but cannot delete data. 6 tools only read.

2 tools read private data (list_models and get_stats); 1 tool brings in text other people can write (list_models).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Can't be undone 3Claude Code: ask
  • claim_topupCredit a stablecoin transfer to our address that has no matching order (or a non-exact amount).No findings

    Why it is in this group

    • The name "claim_topup" says "topup": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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.
  • create_topupCreate a stablecoin top-up order.No findings

    Why it is in this group

    • The name "create_topup" says "create": a word for a change.
    • The name "create_topup" also says "topup": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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_topupConfirm a top-up after sending funds, by order id and transaction hash/signature.No findings

    Why it is in this group

    • The name "verify_topup" says "topup": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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).
Changes things 3Claude Code: ask
  • chat_completionRun a chat completion billed to a tai_ key's credits.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run a chat completion billed to a tai_ key's credits.
  • quotePrice 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 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • set_capSet spend controls on a tai_ key: total spend cap, daily limit (UTC day) and per-request max, in USD.No findings

    Why it is in this group

    • The name "set_cap" says "set": a word for a change.
    Description, as the server wrote it
    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.
Only reads 6Show 6 read-only tools
  • get_balanceGet the credit balance, spend cap and amount spent for a tai_ API key.No findings

    Why it is in this group

    • The name "get_balance" says "get": a word for reading.
    Description, as the server wrote it
    Get the credit balance, spend cap and amount spent for a tai_ API key.
  • get_statsPublic platform stats from our database (tokens and requests in the last 24h, keys created, top models).Reads private dataNo findings

    Why it is in this group

    • The name "get_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "database": it reads databases.
    Description, as the server wrote it
    Public platform stats from our database (tokens and requests in the last 24h, keys created, top models). Real numbers only.
  • get_usageUsage and audit log for a tai_ key: recent charges (model, tokens, cost), top-ups, last-24h totals, balance and limits.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    Usage and audit log for a tai_ key: recent charges (model, tokens, cost), top-ups, last-24h totals, balance and limits.
  • list_modelsList servable text chat models with USD prices (pricing.vs_list vs maker list price).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_models" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "chat": it reads messages.
    • untrusted-inputThe description's first sentence says "list" and "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    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_price_changesPrice-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.No findings

    Why it is in this group

    • The name "list_price_changes" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:23 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (3 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://pay.trustai.center/mcp: tools/list returned 12 tools to an anonymous client, including create_topup (irreversible), verify_topup (irreversible), claim_topup (irreversible), quote (write), set_cap (write) and 1 more

    What this check looks for

Posture changes

  1. Nov 3, 2026
    • Tools that change things, listed without credentials: 5 to 6

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 1 changed.+2 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 6.View diff
    • Tools that change things, listed without credentials: 5 to 6

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trustai-pay https://pay.trustai.center/mcp
claude mcp add --transport http trustai-pay https://pay.trustai.center/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trustai-pay__list_models",
      "mcp__trustai-pay__list_trending",
      "mcp__trustai-pay__list_price_changes",
      "mcp__trustai-pay__get_balance",
      "mcp__trustai-pay__get_usage",
      "mcp__trustai-pay__get_stats"
    ],
    "ask": [
      "mcp__trustai-pay__quote",
      "mcp__trustai-pay__create_topup",
      "mcp__trustai-pay__verify_topup",
      "mcp__trustai-pay__claim_topup",
      "mcp__trustai-pay__set_cap",
      "mcp__trustai-pay__chat_completion"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trustai-pay. Review it before you use it.

Capability tags behind 2 rules
  • mcp__trustai-pay__list_models private-data, untrusted-input
  • mcp__trustai-pay__get_stats private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/center.trustai.pay/trustai-pay/verify?hash=9b5260a94fe42d2f7b08418023171a83a438b8e33f9889ce66530de14914e809" | jq -e '.changed == false'

Pinned hash 9b5260a94fe4, from Nov 9, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/center.trustai.pay/trustai-pay/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for center.trustai.pay/trustai-pay
[![Anlyon Radar](https://radar.anlyon.com/badge/center.trustai.pay/trustai-pay.svg)](https://radar.anlyon.com/servers/center.trustai.pay/trustai-pay)

Source: MCP Registry. Synced Oct 25, 2026, 17:21 UTC.

trustai.center pay MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the trustai.center pay MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the trustai.center pay MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the trustai.center pay MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: create_topup, verify_topup and claim_topup.

What tools does the trustai.center pay MCP server have?

12 tools: 3 irreversible, 3 write, 6 read. create_topup, verify_topup, claim_topup, quote, set_cap, chat_completion, list_models, list_trending and 4 more.

Does the trustai.center pay MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the trustai.center pay MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the trustai.center pay MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.