Remote MCP · Endpoint
ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more MCP server
No. ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more answered an MCP handshake 47 minutes ago.
UpLast checked 47 minutes ago
Server URL
https://compliancecn.netlify.app/mcp?src=official_registry
The last check completed an MCP handshake.
- Registry name
- io.github.liamohtee/agentcn
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 439 ms
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 4 checks from 4 checks
- Described by its publisher as
- Source-cited EU/UK/US/AU market-access checks for Amazon and cross-border product compliance.
- Repository
- https://github.com/liamohtee/AgentCN
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 47 minutes ago | Handshake completed | 439 ms |
| 1 hour ago | Handshake completed | 939 ms |
| 1 day ago | Handshake completed | 914 ms |
| 2 days ago | Handshake completed | 420 ms |
The last 4 checks. Full history is kept for 30 days; the all-time counter stands at 4 responding of 4.
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 ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more and makes no claim about it beyond what these checks measured.