GoAI Moat Export Compliance
REMOTE · COMPLIANCE.MCP.GOAIMOAT.COM · SCANNED SEP 28
Export compliance & HS code lookup for cross-border electronics sellers and factories.
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 → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 434 tokens (~144/item across 3 items; 3 tools + 0 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 Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the GoAI Moat Export Compliance MCP server?
GoAI Moat Export Compliance is a hosted endpoint at https://compliance.mcp.goaimoat.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · compliance.mcp.goaimoat.com
claude mcp add --transport http com-goaimoat-export-compliance 'https://compliance.mcp.goaimoat.com/mcp'
{
"mcpServers": {
"com-goaimoat-export-compliance": {
"url": "https://compliance.mcp.goaimoat.com/mcp"
}
}
} {
"servers": {
"com-goaimoat-export-compliance": {
"type": "http",
"url": "https://compliance.mcp.goaimoat.com/mcp"
}
}
} [mcp_servers.com-goaimoat-export-compliance] url = "https://compliance.mcp.goaimoat.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-goaimoat-export-compliance": {
"type": "remote",
"url": "https://compliance.mcp.goaimoat.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-goaimoat-export-compliance --url 'https://compliance.mcp.goaimoat.com/mcp' --transport streamable-http
mcp_servers:
com-goaimoat-export-compliance:
url: "https://compliance.mcp.goaimoat.com/mcp" {
"McpServers": {
"com-goaimoat-export-compliance": {
"Transport": "http",
"Url": "https://compliance.mcp.goaimoat.com/mcp"
}
}
} assistant mcp add com-goaimoat-export-compliance -t streamable-http -u 'https://compliance.mcp.goaimoat.com/mcp'
{
"mcpServers": {
"com-goaimoat-export-compliance": {
"type": "http",
"url": "https://compliance.mcp.goaimoat.com/mcp"
}
}
} 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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 65
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 28 Sept 2026 · Probed https://compliance.mcp.goaimoat.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=compliance.mcp.goaimoat.com | CN=YE2,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5d83fc8c171b670d0754b67a33a9a46450f |
| SANs: compliance.mcp.goaimoat.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of compliance.mcp.goaimoat.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| goaimoat.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://compliance.mcp.goaimoat.com/mcp | Verified | 200 | |
| http (plaintext) | http://compliance.mcp.goaimoat.com/mcp | HTTPS enforced | 301 | https://compliance.mcp.goaimoat.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_compliance_checklist Export Compliance Checklist ~64
生成出口到目标市场的分阶段合规自检清单。
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| license_key | string | – | – |
| market | string | – | 目标市场，可选 EU / US / UK / JP（默认 EU）。 |
Structured output declared, but exposes no named fields.
No examples provided.
hs_code_reference Hs Code Reference ~80
按产品关键词查 HS 编码归类速查（6 位全球统一编码层级）。
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| keyword | string | yes | 产品关键词（中英文均可，如 "充电器" / "usb charger" / "连接器" / "耳机"）。 |
| license_key | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
market_access_requirements Market Access Requirements ~152
查询某产品品类进入目标市场的强制认证/标签/环保要求。 覆盖电子配件常见品类：连接器、充电器、线缆、音频（耳机/音箱）、 无线（蓝牙/WiFi）、移动电源、PCB、显示器、手机壳、玩具。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 产品品类（中英文均可，如 "connector" / "连接器" / "charger" / "耳机"）。 |
| string | – | – | |
| license_key | string | – | – |
| market | string | – | 目标市场，可选 EU / US / UK / JP（默认 EU）。 |
Structured output declared, but exposes no named fields.
No examples provided.
What is the GoAI Moat Export Compliance MCP server?
GoAI Moat Export Compliance is an MCP server listed in the public MCP registry as com.goaimoat/export-compliance. Export compliance & HS code lookup for cross-border electronics sellers and factories. This page covers its hosted endpoint (https://compliance.mcp.goaimoat.com/mcp).
Is the GoAI Moat Export Compliance MCP server safe to use?
GoAI Moat Export Compliance scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GoAI Moat Export Compliance MCP server expose?
GoAI Moat Export Compliance exposes 3 tools: market_access_requirements, hs_code_reference, export_compliance_checklist. Their descriptions and schemas cost roughly 296 tokens of context every time the server is loaded.
Does the GoAI Moat Export Compliance MCP server require authentication?
No. We connected to GoAI Moat Export Compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GoAI Moat Export Compliance MCP server still maintained?
GoAI Moat Export Compliance is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.