ComplianceCN — toys, batteries, cosmetics, food contact: CE, GPSR, UN 38.3, CPC/GCC and more
REMOTE · COMPLIANCECN.NETLIFY.APP · SCANNED AUG 17
Source-cited EU/UK/US/AU market-access checks for Amazon and cross-border product compliance.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 7025 tokens (~540/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · compliancecn.netlify.app
claude mcp add --transport http liamohtee-agentcn https://compliancecn.netlify.app/mcp?src=official_registry
[mcp_servers.liamohtee-agentcn] url = "https://compliancecn.netlify.app/mcp?src=official_registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"liamohtee-agentcn": {
"type": "remote",
"url": "https://compliancecn.netlify.app/mcp?src=official_registry",
"enabled": true
}
}
} openclaw mcp add liamohtee-agentcn --url https://compliancecn.netlify.app/mcp?src=official_registry --transport streamable-http
mcp_servers:
liamohtee-agentcn:
url: "https://compliancecn.netlify.app/mcp?src=official_registry" {
"mcpServers": {
"liamohtee-agentcn": {
"type": "http",
"url": "https://compliancecn.netlify.app/mcp?src=official_registry"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 +1
- Server version: 0.3.2 → 0.3.4 functional
- 14 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Aug 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Aug 2026 · Probed https://compliancecn.netlify.app/mcp?src=official_registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.netlify.app,O=Netlify\, Inc,L=San Francisco,ST=California,C=US | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 16 Feb 2026 | 19 Mar 2027 | ECDSA 256 | SHA256-RSA | cd5d0afb0611b5bd9d692535c0ca7c4 |
| SANs: *.netlify.app, netlify.app | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
DNSSEC insecure
Validation of compliancecn.netlify.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| netlify.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://compliancecn.netlify.app/mcp?src=official_registry | Verified | 200 | |
| http (plaintext) | http://compliancecn.netlify.app/mcp?src=official_registry | HTTPS enforced | 301 | https://compliancecn.netlify.app/mcp?src=official_registry |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_amazon_compliance_request Amazon or another marketplace asked for compliance files ~945
Use when Amazon or another marketplace has asked a seller for compliance files or documents -- for example "Amazon asked me for compliance paperwork", "my listing was taken down pending documents", or "the platform wants safety evidence". Returns the evidence a marketplace typically requests for this product and destination market, which items the seller already holds, and what is still outstanding. Answers immediately from the published ruleset: no case, no account, no follow-up call. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| applicable_modules | array | – | Optional additional modules that should be assessed together with the primary category, for example toys plus battery-electronics. |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | – | Optional structured category hint. Canonical IDs and common English/Chinese labels are accepted. Omit when product_description contains enough information for extraction. |
| claims_therapeutic | boolean | – | – |
| clarification_answer | string | – | Continuation shortcut for the exact same case_id when answering questions_required. Send the seller's natural-language answer here; the service restores and merges the previous canonical product prof… |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| evidence_held | array | – | – |
| evidence_inventory_complete | boolean | – | True only when evidence_notes/evidence_text and evidence_held together form a complete inventory. Otherwise unprovided applicable evidence remains unknown, not missing. |
| evidence_notes | string | – | Document and evidence information known by the seller or agent: filenames, supplier claims, models, standards, issuers, dates, or extracted key text. Explicit evidence may be mapped to evidence IDs;… |
| evidence_observations | array | – | Sanitised document observations that may continue between workflow stages: apparent type, filename/reference, models, organisation, date, identifiers, standards, confidence and unresolved issues. Do… |
| evidence_text | string | – | Document/evidence information already known or extracted by an agent. File upload is optional and separate. Do not paste sensitive certificates or full reports into agent chat. |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Canonical values are zh or en. Common English and Chinese labels are accepted during preflight and normalized. |
| markets | array | – | Optional destination-market hints. Omit when product_description names the destination. |
| product_description | string | – | Preferred first input: describe the product, destination market, sales channel and any known supplier documents in plain language. The tool extracts a preliminary profile and fills the internal check… |
| product_name | string | – | Human-readable product or SKU name |
| repeated_use | string | – | – |
| sales_channel | string | – | Sales channel. Canonical values are amazon, other_marketplace, own_site or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| sells_in_california | boolean | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude decision rules not checked against primary sources |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
check_battery_transport_documents Forwarder will not take the battery product ~949
Use when a freight forwarder, courier or carrier has refused or queried a battery product -- for example "my forwarder will not ship the lithium battery", "they want the UN 38.3 report", or "the airline rejected my dangerous-goods paperwork". Returns whether a UN 38.3 test summary applies to this cell and pack, the shipping marks required, and the transport documents a forwarder usually asks for. Answers immediately from the published ruleset. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| applicable_modules | array | – | Optional additional modules that should be assessed together with the primary category, for example toys plus battery-electronics. |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | – | Optional structured category hint. Canonical IDs and common English/Chinese labels are accepted. Omit when product_description contains enough information for extraction. |
| claims_therapeutic | boolean | – | – |
| clarification_answer | string | – | Continuation shortcut for the exact same case_id when answering questions_required. Send the seller's natural-language answer here; the service restores and merges the previous canonical product prof… |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| evidence_held | array | – | – |
| evidence_inventory_complete | boolean | – | True only when evidence_notes/evidence_text and evidence_held together form a complete inventory. Otherwise unprovided applicable evidence remains unknown, not missing. |
| evidence_notes | string | – | Document and evidence information known by the seller or agent: filenames, supplier claims, models, standards, issuers, dates, or extracted key text. Explicit evidence may be mapped to evidence IDs;… |
| evidence_observations | array | – | Sanitised document observations that may continue between workflow stages: apparent type, filename/reference, models, organisation, date, identifiers, standards, confidence and unresolved issues. Do… |
| evidence_text | string | – | Document/evidence information already known or extracted by an agent. File upload is optional and separate. Do not paste sensitive certificates or full reports into agent chat. |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Canonical values are zh or en. Common English and Chinese labels are accepted during preflight and normalized. |
| markets | array | – | Optional destination-market hints. Omit when product_description names the destination. |
| product_description | string | – | Preferred first input: describe the product, destination market, sales channel and any known supplier documents in plain language. The tool extracts a preliminary profile and fills the internal check… |
| product_name | string | – | Human-readable product or SKU name |
| repeated_use | string | – | – |
| sales_channel | string | – | Sales channel. Canonical values are amazon, other_marketplace, own_site or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| sells_in_california | boolean | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude decision rules not checked against primary sources |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
check_eu_declaration_basis EU declaration basis ~959
Use when a buyer, customs authority or distributor wants the EU Declaration of Conformity -- for example "customs is asking for the DoC", "my buyer wants the declaration", or "which directives do I cite?". Returns the legislation and standards a Declaration of Conformity would cite for this product, the evidence held against each, and the fields that still need confirming before anyone signs. This maps the basis for a declaration; it does not issue or sign one. Answers immediately from the published ruleset. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| applicable_modules | array | – | Optional additional modules that should be assessed together with the primary category, for example toys plus battery-electronics. |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | – | Optional structured category hint. Canonical IDs and common English/Chinese labels are accepted. Omit when product_description contains enough information for extraction. |
| claims_therapeutic | boolean | – | – |
| clarification_answer | string | – | Continuation shortcut for the exact same case_id when answering questions_required. Send the seller's natural-language answer here; the service restores and merges the previous canonical product prof… |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| evidence_held | array | – | – |
| evidence_inventory_complete | boolean | – | True only when evidence_notes/evidence_text and evidence_held together form a complete inventory. Otherwise unprovided applicable evidence remains unknown, not missing. |
| evidence_notes | string | – | Document and evidence information known by the seller or agent: filenames, supplier claims, models, standards, issuers, dates, or extracted key text. Explicit evidence may be mapped to evidence IDs;… |
| evidence_observations | array | – | Sanitised document observations that may continue between workflow stages: apparent type, filename/reference, models, organisation, date, identifiers, standards, confidence and unresolved issues. Do… |
| evidence_text | string | – | Document/evidence information already known or extracted by an agent. File upload is optional and separate. Do not paste sensitive certificates or full reports into agent chat. |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Canonical values are zh or en. Common English and Chinese labels are accepted during preflight and normalized. |
| markets | array | – | Optional destination-market hints. Omit when product_description names the destination. |
| product_description | string | – | Preferred first input: describe the product, destination market, sales channel and any known supplier documents in plain language. The tool extracts a preliminary profile and fills the internal check… |
| product_name | string | – | Human-readable product or SKU name |
| repeated_use | string | – | – |
| sales_channel | string | – | Sales channel. Canonical values are amazon, other_marketplace, own_site or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| sells_in_california | boolean | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude decision rules not checked against primary sources |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
check_label_and_packaging Label and packaging review ~935
Use when a seller is unsure their label, artwork or packaging is correct -- for example "is my CE label right?", "what warnings do I need on the box?", or "does the packaging need an importer address?". Returns the marks, symbols, warning language and responsible-entity details the destination market requires on the artwork, and which of them are evidenced. Answers immediately from the published ruleset. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| applicable_modules | array | – | Optional additional modules that should be assessed together with the primary category, for example toys plus battery-electronics. |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | – | Optional structured category hint. Canonical IDs and common English/Chinese labels are accepted. Omit when product_description contains enough information for extraction. |
| claims_therapeutic | boolean | – | – |
| clarification_answer | string | – | Continuation shortcut for the exact same case_id when answering questions_required. Send the seller's natural-language answer here; the service restores and merges the previous canonical product prof… |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| evidence_held | array | – | – |
| evidence_inventory_complete | boolean | – | True only when evidence_notes/evidence_text and evidence_held together form a complete inventory. Otherwise unprovided applicable evidence remains unknown, not missing. |
| evidence_notes | string | – | Document and evidence information known by the seller or agent: filenames, supplier claims, models, standards, issuers, dates, or extracted key text. Explicit evidence may be mapped to evidence IDs;… |
| evidence_observations | array | – | Sanitised document observations that may continue between workflow stages: apparent type, filename/reference, models, organisation, date, identifiers, standards, confidence and unresolved issues. Do… |
| evidence_text | string | – | Document/evidence information already known or extracted by an agent. File upload is optional and separate. Do not paste sensitive certificates or full reports into agent chat. |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Canonical values are zh or en. Common English and Chinese labels are accepted during preflight and normalized. |
| markets | array | – | Optional destination-market hints. Omit when product_description names the destination. |
| product_description | string | – | Preferred first input: describe the product, destination market, sales channel and any known supplier documents in plain language. The tool extracts a preliminary profile and fills the internal check… |
| product_name | string | – | Human-readable product or SKU name |
| repeated_use | string | – | – |
| sales_channel | string | – | Sales channel. Canonical values are amazon, other_marketplace, own_site or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| sells_in_california | boolean | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude decision rules not checked against primary sources |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
check_us_import_certification US certification and entry filing ~945
Use when a US importer, customs broker or buyer needs certification or entry-filing data -- for example "my importer wants a CPC", "do I need a GCC?", "what does CBP need at entry?", or "the buyer asked for the FCC SDoC". Returns whether a CPC or GCC applies, the supporting test evidence, the US responsible-party details, and the same data needed at entry. Answers immediately from the published ruleset. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| applicable_modules | array | – | Optional additional modules that should be assessed together with the primary category, for example toys plus battery-electronics. |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | – | Optional structured category hint. Canonical IDs and common English/Chinese labels are accepted. Omit when product_description contains enough information for extraction. |
| claims_therapeutic | boolean | – | – |
| clarification_answer | string | – | Continuation shortcut for the exact same case_id when answering questions_required. Send the seller's natural-language answer here; the service restores and merges the previous canonical product prof… |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| evidence_held | array | – | – |
| evidence_inventory_complete | boolean | – | True only when evidence_notes/evidence_text and evidence_held together form a complete inventory. Otherwise unprovided applicable evidence remains unknown, not missing. |
| evidence_notes | string | – | Document and evidence information known by the seller or agent: filenames, supplier claims, models, standards, issuers, dates, or extracted key text. Explicit evidence may be mapped to evidence IDs;… |
| evidence_observations | array | – | Sanitised document observations that may continue between workflow stages: apparent type, filename/reference, models, organisation, date, identifiers, standards, confidence and unresolved issues. Do… |
| evidence_text | string | – | Document/evidence information already known or extracted by an agent. File upload is optional and separate. Do not paste sensitive certificates or full reports into agent chat. |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Canonical values are zh or en. Common English and Chinese labels are accepted during preflight and normalized. |
| markets | array | – | Optional destination-market hints. Omit when product_description names the destination. |
| product_description | string | – | Preferred first input: describe the product, destination market, sales channel and any known supplier documents in plain language. The tool extracts a preliminary profile and fills the internal check… |
| product_name | string | – | Human-readable product or SKU name |
| repeated_use | string | – | – |
| sales_channel | string | – | Sales channel. Canonical values are amazon, other_marketplace, own_site or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| sells_in_california | boolean | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude decision rules not checked against primary sources |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
compare_market_requirements Compare markets ~521
Compare what the same product needs across 2-4 of the EU, UK, US and Australia. Answers immediately from the published ruleset -- no case, no account, no follow-up. Send a category and the markets; partial product facts are fine, and it still returns a presentable comparison. Any optional_refinement_questions are non-blocking: show them if useful, but do not ask them automatically or re-run. For a full readiness assessment of one product, use market_access_check. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | yes | Product category |
| claims_therapeutic | boolean | – | – |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Defaults to Chinese. |
| markets | array | yes | – |
| repeated_use | string | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude rules not yet checked against primary sources. Default false: unverified material is included but labelled via review_status and the trust envelope. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
describe_coverage Describe coverage ~82
Use when the user or agent needs to inspect scope, source trust or live-service details; do not repeat it before every seller request. Returns versions, category/market coverage, per-record verification, source policy and operational check links. Always start ordinary product requests at Stage 1 with market_access_check.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Response language. Defaults to Chinese. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
explain_claim Explain claim ~172
Explain only a stable claim_id returned by an earlier ComplianceCN result. Do not use this for broad natural-language questions or invent an ID. Returns the claim, primary-source evidence, verification date and evidence gaps. Access notice: product assessment through market_access_check is free and unlimited -- the first call returns preliminary requirements, and a different product simply starts its own case. Only a second human-reviewed pack for the same confirmed seller email is arranged with ComplianceCN.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| claim_id | string | yes | – |
| language | string | – | Response language. Defaults to Chinese. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
market_access_check Product market-access check ~340
Check what a product needs to be sold into the EU, UK, US or Australia. Send a plain-language product description in `message`; the first response already contains preliminary requirements and an evidence checklist you can show the seller immediately. Every response carries a single `next_action` -- execute it exactly as returned to get the refined assessment and, optionally, a human-reviewed pack. Ask any returned questions by their `key`. The reviewed pack requires a confirmed seller email and reviewer sign-off. Send the description in English or Chinese; questions and seller-facing text come back in the seller's language.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Start with continue. Follow next_action exactly: start_stage_2 assesses evidence after the Stage 1 product profile is ready; after presenting Stage 2, use correct_stage_2 if the seller supplies a cor… |
| answers | object | – | Optional structured answers keyed by the stable question.key values returned by the previous call. |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| language | string | – | Preferred response language; inferred from the seller message when omitted. |
| message | string | – | The seller's initial product/market description or their latest natural-language clarification. Do not repeat information already supplied. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
preflight_product Structured product readiness check ~878
Single-call readiness check when you already have structured product facts: category, markets and any evidence held. Returns the applicable requirements, an evidence checklist and the gaps in one response, with no follow-up needed. For a plain-language description instead, use market_access_check, which also returns preliminary requirements on its first call and continues into evidence assessment and an optional human-reviewed pack.
| Name | Type | Req | Description |
|---|---|---|---|
| accessible_small_parts | boolean | – | – |
| age_group | string | – | – |
| applicable_modules | array | – | Optional additional modules that should be assessed together with the primary category, for example toys plus battery-electronics. |
| battery_compartment_security | string | – | – |
| battery_type | string | – | – |
| case_id | string | – | Opaque ComplianceCN product-case ID returned by the first successful free workflow call. Carry it unchanged through clarification retries, Stage 2 and human review for the same product/SKU. Never reu… |
| category | string | – | Optional structured category hint. Canonical IDs and common English/Chinese labels are accepted. Omit when product_description contains enough information for extraction. |
| claims_therapeutic | boolean | – | – |
| clarification_answer | string | – | Continuation shortcut for the exact same case_id when answering questions_required. Send the seller's natural-language answer here; the service restores and merges the previous canonical product prof… |
| contact_duration | string | – | – |
| contact_temperature | string | – | – |
| eu_destination | string | – | – |
| evidence_held | array | – | – |
| evidence_inventory_complete | boolean | – | True only when evidence_notes/evidence_text and evidence_held together form a complete inventory. Otherwise unprovided applicable evidence remains unknown, not missing. |
| evidence_notes | string | – | Document and evidence information known by the seller or agent: filenames, supplier claims, models, standards, issuers, dates, or extracted key text. Explicit evidence may be mapped to evidence IDs;… |
| evidence_observations | array | – | Sanitised document observations that may continue between workflow stages: apparent type, filename/reference, models, organisation, date, identifiers, standards, confidence and unresolved issues. Do… |
| evidence_text | string | – | Document/evidence information already known or extracted by an agent. File upload is optional and separate. Do not paste sensitive certificates or full reports into agent chat. |
| food_contact_material | string | – | – |
| food_type | string | – | – |
| has_battery | boolean | – | – |
| has_radio | boolean | – | – |
| includes_mains_charger | boolean | – | – |
| ingredients_reviewed | boolean | – | – |
| is_childrens_product | boolean | – | Whether the product is marketed as a children's product; keep unknown when not established. |
| is_electrically_operated | boolean | – | Whether the toy is electrically operated, including mains-powered or battery-powered operation. |
| is_sunscreen | boolean | – | – |
| language | string | – | Response language. Canonical values are zh or en. Common English and Chinese labels are accepted during preflight and normalized. |
| markets | array | – | Optional destination-market hints. Omit when product_description names the destination. |
| product_description | string | – | Preferred first input: describe the product, destination market, sales channel and any known supplier documents in plain language. The tool extracts a preliminary profile and fills the internal check… |
| product_name | string | – | Human-readable product or SKU name |
| repeated_use | string | – | – |
| sales_channel | string | – | Sales channel. Canonical values are amazon, other_marketplace, own_site or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| sells_in_california | boolean | – | – |
| supply_chain_role | string | – | Supply-chain role. Canonical values are manufacturer, importer, distributor, marketplace_seller or unknown. Common natural-language English and Chinese labels are accepted and normalized. |
| toy_chemical_assessment_complete | boolean | – | – |
| verified_only | boolean | – | Exclude decision rules not checked against primary sources |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.
watch_product_regulatory_changes Email me when the rules for this product change ~259
Start free email alerts for regulatory changes affecting a product already checked here. Use when a seller says they want to be told if the rules change -- for example "let me know if this changes", "can you monitor this for me?", or "email me about updates". Requires a real top-level email and consent_to_alerts=true; there is no payment and no checkout step. Alerts start immediately and cover human-reviewed ComplianceCN changelog updates matching the saved product, market, requirement or rule profile. It does not guarantee detection of every regulatory change. Call only after a product check has produced a usable product/market profile and the seller has explicitly asked to be notified.
| Name | Type | Req | Description |
|---|---|---|---|
| consent_to_alerts | boolean | yes | Must be true. The seller explicitly agrees to save this product profile and receive matched product-change and subscription-service emails. |
| string | yes | Seller email for product-change alerts. Provide only after the seller explicitly asks for the alert subscription. | |
| preflight_result | object | – | The completed preflight result when available. Its requirement, rule and claim IDs improve future change matching. |
| product_profile | object | yes | The same normalized product profile used for the completed preflight. Do not include document contents or unrelated personal data. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
| payload | object | yes | – |
No examples provided.