Chinaready MCP Server
[Chinaready China Market-Entry Search MCP connector – tool definition quality and endpoint health on Glama]
[Listed on ClaudePluginHub]
[Chinaready MCP - Let your AI cite real sources on China market entry | Product Hunt]
Remote MCP server for chinaready.co — the practical guide for Western SaaS, app, and game teams entering Mainland China. Ask about ICP filing and licensing, app-store and game publishing, China cloud regions (AWS China, Azure China, Alibaba Cloud), payments, and compliance; every answer cites its source page.
- Endpoint:
https://mcp.chinaready.co/mcp (Streamable HTTP, stateless)
- Auth: none — public, read-only content
- Host: any Cloudflare Workers-compatible runtime (zero dependencies, zero secrets)
Tools
All tools are read-only (readOnlyHint: true).
Install
Claude — claude.ai → Settings → Connectors → Add custom connector → paste https://mcp.chinaready.co/mcp → choose No sign in → Add.
Claude Code
Cursor — one click:
VS Code — one click (opens the redirect installer):
or in .vscode/mcp.json:
Any MCP client (Windsurf, Zed, LibreChat, …) — remote server, no command, no keys:
Development
The server is a thin stateless proxy over Chinaready's public retrieval API
(search.chinaready.co); it stores nothing and needs no environment
variables. Outbound calls go only to search.chinaready.co (retrieval) and
chinaready.co (article fetch) — no other network destinations.
get_article only fetches chinaready.co pages it has validated
as safe site paths.
Usage tracking
Every RPC message writes one data point to the chinaready_mcp_usage
Analytics Engine dataset (blobs: method, tool, outcome, truncated ua;
retention ~90 days). Method and tool names only — arguments and query content
are never logged.
Prints the daily volume, the RPC funnel (initialize → tools/list →
tools/call), tool-call breakdown with error outcomes, and a client split
(sdk / probe-bot / browser) so real usage can be told apart from the MCP
directory liveness bots. The token needs Analytics Engine Read.
Raw queries go through the Analytics Engine SQL
API
(POST /accounts/{account}/analytics_engine/sql):
License
MIT