Remote MCP · Endpoint

ChinaAPI MCP server

No. ChinaAPI answered an MCP handshake 10 hours ago.

UpLast checked 10 hours 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
681 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.
Listing
From the official MCP registry (active).
Recent checks of ChinaAPI
CheckedResultHandshake
10 hours agoHandshake completed681 ms
3 days agoHandshake completed802 ms
12 days agoHandshake completed657 ms
13 days agoHandshake completed647 ms
14 days agoHandshake completed649 ms
15 days agoHandshake completed719 ms
16 days agoHandshake completed833 ms
17 days agoHandshake completed776 ms
18 days agoHandshake completed673 ms
20 days agoHandshake completed693 ms
22 days agoHandshake completed663 ms
25 days agoHandshake completed653 ms
27 days agoHandshake completed683 ms
30 days agoHandshake completed712 ms

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

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.

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.