Remote MCP · Endpoint

ChinaAPI MCP server

No. ChinaAPI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.chinaapi.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.chinaapi/chinaapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
693 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only ChinaAPI model catalogue, price snapshot, cost estimates and request recipes.
Website
https://dash.chinaapi.ai/agents
Listing
From the official MCP registry (active).
Recent checks of ChinaAPI
CheckedResultHandshake
1 hour agoHandshake completed693 ms
2 days agoHandshake completed663 ms
5 days agoHandshake completed653 ms
7 days agoHandshake completed683 ms
9 days agoHandshake completed712 ms
11 days agoHandshake completed700 ms
13 days agoHandshake completed691 ms
15 days agoHandshake completed686 ms
18 days agoHandshake completed686 ms
19 days agoHandshake completed699 ms
20 days agoHandshake completed692 ms
22 days agoHandshake completed710 ms
23 days agoHandshake completed755 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with ChinaAPI and makes no claim about it beyond what these checks measured.