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.

ChinaAPI

REMOTE · API.CHINAAPI.AI

Read-only ChinaAPI model catalogue, price snapshot, cost estimates and request recipes.

Available components

+3 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 4 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 Security74
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1223 tokens (~305/item across 4 items; 4 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 Management97
  • Stability observed for 29 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

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 4 Nov 2026 · Probed https://api.chinaapi.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.chinaapi.ai CN=YE2,O=Let's Encrypt,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA384 5c35d136f2936c2e0c07401e2acb1568a79
SANs: api.chinaapi.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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.chinaapi.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
chinaapi.ai. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.chinaapi.ai/mcp Verified 200
http (plaintext) http://api.chinaapi.ai/mcp HTTPS enforced 308 https://api.chinaapi.ai/mcp
MCP tools · 4 exposed · ~984 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
chinaapi_estimate_cost ~447

Estimate the USD cost of a workload on one model from its published per-meter prices: Standard, and Paid where it is lower. Pass quantities in the model's own units — tokens for text models, characters for speech synthesis, audio seconds for transcription, requests, images or video seconds for per-call and per-second models; a quantity the model does not price is refused. Tiered models are estimated tier by tier. The result is an estimate, not a quote.

NameTypeReqDescription
audio_input_tokensinteger–Quantity in tokens for the audio_input meter (models billed in tokens).
audio_output_tokensinteger–Quantity in tokens for the audio_output meter (models billed in tokens).
audio_secondsinteger–Quantity in audio seconds for the input meter (models billed in audio_duration).
cache_read_tokensinteger–Quantity in tokens for the cache_read meter (models billed in tokens).
cache_write_1h_tokensinteger–Quantity in tokens for the cache_write_1h meter (models billed in tokens).
cache_write_tokensinteger–Quantity in tokens for the cache_write meter (models billed in tokens).
charactersinteger–Quantity in characters for the input meter (models billed in characters).
context_tokensinteger–Input context length used to choose a context-length tier. Only for models whose tiers depend on context length; defaults to the input and cache tokens.
image_input_tokensinteger–Quantity in tokens for the image_input meter (models billed in tokens).
image_output_tokensinteger–Quantity in tokens for the image_output meter (models billed in tokens).
imagesinteger–Quantity in images for the image_n meter.
input_tokensinteger–Quantity in tokens for the input meter (models billed in tokens).
modelstringyesExact, case-sensitive model ID as returned by chinaapi_list_models.
output_tokensinteger–Quantity in tokens for the output meter (models billed in tokens).
requestsinteger–Quantity in requests for the per_call meter.
video_secondsinteger–Quantity in seconds for the video_second meter.

No output schema declared.

No examples provided.

chinaapi_get_model ~102

Get one model by its exact ID: base URL and endpoints, the Standard and Paid price snapshot per meter with the time it was read and the price-book versions, context window and modalities, capability contract, limits, and ChinaAPI links (model page, a start link to try it, the agents guide). The live price on the model page is authoritative.

NameTypeReqDescription
modelstringyesExact, case-sensitive model ID as returned by chinaapi_list_models.

No output schema declared.

No examples provided.

chinaapi_get_recipe ~214

Get a runnable request for one model — endpoint, headers, JSON body or multipart form, a curl command, and for video the polling step — exactly as ChinaAPI's /agents page shows it. Optionally include the configuration that points a coding agent (Claude Code, Codex, Cursor, …) at ChinaAPI. The request uses $CHINAAPI_KEY; never put a real key into it.

NameTypeReqDescription
agentstring–Also return the configuration that points this coding agent at ChinaAPI, as ChinaAPI's /agents page shows it.
capabilitystring–Which of the model's capabilities the request is for; defaults to its first published capability.
modelstringyesExact, case-sensitive model ID as returned by chinaapi_list_models.
protocolstring–Inbound protocol for text models: openai (/v1/chat/completions), anthropic (/v1/messages) or responses (/v1/responses). Defaults to the agent's protocol, else openai.

No output schema declared.

No examples provided.

chinaapi_list_models ~221

List the models ChinaAPI serves, optionally filtered by capability, task, maker or a model-ID substring. Each entry has the exact model ID, maker, capabilities and tasks, context window, headline Standard prices (and Paid prices where they are lower) and the model's ChinaAPI page. Sorted by maker, then model ID; page with cursor. Use chinaapi_get_model for one model's endpoints, full prices and limits.

NameTypeReqDescription
capabilitystring–Capability direction: text-multimodal (chat, reasoning, coding, vision), image, video, audio-speech or decision.
cursorstring–next_cursor from the previous page.
limitinteger–Models per page.
makerstring–Maker name exactly as returned in maker (case-insensitive), e.g. DeepSeek.
querystring–Case-insensitive substring of the model ID.
taskstring–A task within a capability, e.g. image-to-video or transcription. Must belong to capability when both are given.

No output schema declared.

No examples provided.

Install

How do I install the ChinaAPI MCP server?

ChinaAPI is a hosted endpoint at https://api.chinaapi.ai/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 · api.chinaapi.ai

# add to Claude Code
claude mcp add --transport http ai-chinaapi-chinaapi 'https://api.chinaapi.ai/mcp'
Common questions

What is the ChinaAPI MCP server?

ChinaAPI is an MCP server listed in the public MCP registry as ai.chinaapi/chinaapi. Read-only ChinaAPI model catalogue, price snapshot, cost estimates and request recipes. This page covers its hosted endpoint (https://api.chinaapi.ai/mcp).

Is the ChinaAPI MCP server safe to use?

ChinaAPI scores 83 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 ChinaAPI MCP server expose?

ChinaAPI exposes 4 tools: chinaapi_estimate_cost, chinaapi_get_model, chinaapi_get_recipe, chinaapi_list_models. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

Does the ChinaAPI MCP server require authentication?

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

Is the ChinaAPI MCP server still maintained?

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