Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TopxAI Models

REMOTE · API.TOPXAI.XYZ

Ask Claude, GPT, Grok, GLM, Kimi or DeepSeek from your client; token price plus a $0.001 call fee.

Available components

+3 this week 66 Trust /100

Last scanned (16 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 754 tokens (~251/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ask_model" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 4 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 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.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 63

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://api.topxai.xyz/mcp/models

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.topxai.xyz CN=YE1,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA384 6ad291aabcc5d335e8c29d6b10301f81c34
SANs: api.topxai.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.topxai.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
xyz. DS published 3599, 18130 8, 8 Verified
topxai.xyz. No DS 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=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.topxai.xyz/mcp/models Verified 200
http (plaintext) http://api.topxai.xyz/mcp/models HTTPS enforced 308 https://api.topxai.xyz/mcp/models
MCP tools · 3 exposed · ~570 tokens

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 →

Tool Tokens
ask_model ~293

Send a prompt to one text model of the TopxAI catalogue and return its reply. The models reason before they answer and the reasoning counts toward max_output_tokens, so leave at least 4096 tokens for a full answer or pass a lower reasoning_effort. Billed at the model's token price, reasoning included, plus a $0.001 call fee; the reply reports the exact charge.

NameTypeReqDescription
max_cost_usdnumber–Refuse the call, before anything is billed, when its estimated cost (prompt, max_output_tokens and the call fee) exceeds this amount.
max_output_tokensinteger–Upper bound on the reply, reasoning included; the reasoning itself is not returned. Below 4096 a model may stop before writing any text, and that call is still charged.
modelstringyesModel to ask; list_models shows the choices and prices.
promptstringyesThe user message sent to the model. Include every piece of context the model needs; it sees nothing else.
reasoning_effortstring–Optional thinking effort. Each model takes its own set and list_models shows them with the default, which applies when this is omitted. A lower effort answers sooner and costs less; the reasoning is…
systemstring–Optional system prompt.
temperaturenumber–Optional sampling temperature.
NameTypeReqDescription
call_fee_usdnumber––
chargedboolean–Whether the wallet was debited for this call.
charged_usdnumber–The recorded wallet debit in USD, model price and call fee included.
errorobject–Present on a failed call: category (client, wallet, topxai, upstream, budget), message, charged, charged_usd.
finish_reasonstring––
modelstring––
reasoning_effortstring–The effort the call asked for; the model's default when it named none.
request_idstring–The relay request id; the same id appears in the usage log.
routestring––
usageobject––

No examples provided.

judge ~241

Ask TypeSafe's Jev (a System One model) typed questions about a piece of text and get calibrated numbers back, not prose: a probability for a yes/no question (type noul), one option with a probability per option (type choice, with criteria), or a value on a scale with a probability per anchor (type score, with anchors). Billed at Jev's input-token price plus a $0.001 call fee.

NameTypeReqDescription
modelstring–System One model.
questionsobjectyesQuestion id to typed question. Each question is {"type": "noul" | "choice" | "score", "instructions": "one question a careful reader could answer from the state alone"}. noul may add "criteria": {"tr…
statestringyesThe text the questions are about: a ticket, a log excerpt, a document, a transcript.
NameTypeReqDescription
answersobject–Question id to answer: {type, noul} for a probability, {type, choice, confidence, probabilities} for a choice, {type, score, confidence, probabilities} for a score.
call_fee_usdnumber––
chargedboolean–Whether the wallet was debited for this call.
charged_usdnumber–The recorded wallet debit in USD, model price and call fee included.
errorobject–Present on a failed call: category (client, wallet, topxai, upstream, budget), message, charged, charged_usd.
modelstring––
request_idstring–The relay request id; the same id appears in the usage log.
routestring––
usageobject––

No examples provided.

list_models ~36

List the text models this API key can ask, with their USD prices per million tokens, the reasoning efforts each takes and the call fee.

Input schema present but exposes no named parameters.

NameTypeReqDescription
call_fee_usdnumber––
modelsarray––

No examples provided.

Install

How do I install the TopxAI Models MCP server?

TopxAI Models is a hosted endpoint at https://api.topxai.xyz/mcp/models, 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 · api.topxai.xyz

# add to Claude Code
claude mcp add --transport http xyz-topxai-api-models 'https://api.topxai.xyz/mcp/models'
Common questions

What is the TopxAI Models MCP server?

TopxAI Models is an MCP server listed in the public MCP registry as xyz.topxai.api/models. Ask Claude, GPT, Grok, GLM, Kimi or DeepSeek from your client; token price plus a $0.001 call fee. This page covers its hosted endpoint (https://api.topxai.xyz/mcp/models).

Is the TopxAI Models MCP server safe to use?

TopxAI Models scores 66 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 TopxAI Models MCP server expose?

TopxAI Models exposes 3 tools: list_models, ask_model, judge. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.

Does the TopxAI Models MCP server require authentication?

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

Is the TopxAI Models MCP server still maintained?

TopxAI Models is still listed as active in the MCP registry. We last reached this channel on 21 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 TopxAI Models MCP server?

VerifyMCP ran 12 checks on TopxAI Models, 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 TopxAI Models: 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.