Is io.github.liamohtee/agentcn up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | compliancecn 0.3.4 |
| Answered in | 2006 ms |
| Endpoint checked | https://compliancecn.netlify.app/mcp?src=official_registry |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion` (and 4 more). A2A 0.3 shape./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://compliancecn.netlify.app/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://compliancecn.netlify.app with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 11 tools: check_amazon_compliance_request, check_battery_transport_documents, check_eu_declaration_basis, check_label_and_packaging, check_us_import_certification, compare_market_requirements, describe_coverage, explain_claim, market_access_check, preflight_product, watch_product_regulatory_changes.
Its tools changed between 2026-09 and 2026-10:
check_amazon_compliance_request: description changedcheck_battery_transport_documents: description changedcheck_eu_declaration_basis: description changedcheck_label_and_packaging: description changedcheck_us_import_certification: description changedcompare_market_requirements: description changeddescribe_coverage: description, input schema changedexplain_claim: description changedmarket_access_check: description, input schema changedpreflight_product: description changedwatch_product_regulatory_changes: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.github.liamohtee/agentcn |
|---|---|
| Title | ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more |
| Description | Source-cited EU/UK/US/AU market-access checks for Amazon and cross-border product compliance. |
| Endpoint | https://compliancecn.netlify.app/mcp?src=official_registry |
| Publisher repository | https://github.com/liamohtee/AgentCN |
| Version | 0.3.4 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt