Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MingXi Export Control

REMOTE · API.MINGXIAPI.COM · SCANNED SEP 29

China trade compliance: 2026 tariffs, export-control entities, dual-use licenses & FTA origin rules.

62 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 342 tokens (~57/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the MingXi Export Control MCP server?

MingXi Export Control is a hosted endpoint at https://api.mingxiapi.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 · api.mingxiapi.com

# add to Claude Code
claude mcp add --transport http mingxi888888-cyber-export-control 'https://api.mingxiapi.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "mingxi888888-cyber-export-control": {
      "url": "https://api.mingxiapi.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mingxi888888-cyber-export-control": {
      "type": "http",
      "url": "https://api.mingxiapi.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.mingxi888888-cyber-export-control]
url = "https://api.mingxiapi.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mingxi888888-cyber-export-control": {
      "type": "remote",
      "url": "https://api.mingxiapi.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mingxi888888-cyber-export-control --url 'https://api.mingxiapi.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mingxi888888-cyber-export-control:
    url: "https://api.mingxiapi.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mingxi888888-cyber-export-control": {
      "Transport": "http",
      "Url": "https://api.mingxiapi.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add mingxi888888-cyber-export-control -t streamable-http -u 'https://api.mingxiapi.com/mcp'
// mcp.json
{
  "mcpServers": {
    "mingxi888888-cyber-export-control": {
      "type": "http",
      "url": "https://api.mingxiapi.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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
  • 27 Sept 26 0
    • Tool “query_dualuse” rewrote its description, which is the text the model reads security
    • Schema quality: 51 → 57 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
  • 26 Sept 26 61

    First indexed and scored.

Diagnostics

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 29 Sept 2026 · Probed https://api.mingxiapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mingxiapi.com CN=YE1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 651416b9dc6370d80d89b468c32f0160bdd
SANs: *.mingxiapi.com, mingxiapi.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 api.mingxiapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mingxiapi.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://api.mingxiapi.com/mcp Verified 200
http (plaintext) http://api.mingxiapi.com/mcp HTTPS enforced 301 https://api.mingxiapi.com/mcp
MCP tools · 6 exposed · ~305 tokens

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 →

Tool Tokens
query_any ~47

Auto-route query across all datasets. Best for ambiguous searches (e.g. 'lithium battery', '无人机').

NameTypeReqDescription
keywordstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

query_dualuse ~74

Search dual-use items & technologies: license catalogue (2026, HS-based) AND export control list (ECCN-coded, performance-threshold-based). Use HS code, ECCN code (e.g. 1C351), or technical description.

NameTypeReqDescription
keywordstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

query_entity ~40

Search export control / sanctions entity lists (merged across lists). Use company or individual name.

NameTypeReqDescription
keywordstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

query_fta_origin ~51

Search FTA product-specific rules of origin (25 agreements incl. RCEP, ASEAN, Korea) by HS code or product keyword.

NameTypeReqDescription
keywordstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

query_prohibited ~40

Search prohibited import/export goods catalogues (all batches) by keyword or HS code.

NameTypeReqDescription
keywordstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

query_tariff ~53

Search China 2026 import tariff schedule by HS code or keyword. Returns MFN/provisional/agreement/preferential/general rates. dataset optional.

NameTypeReqDescription
keywordstringyes–
limitinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the MingXi Export Control MCP server?

MingXi Export Control is an MCP server listed in the public MCP registry as io.github.mingxi888888-cyber/export-control. China trade compliance: 2026 tariffs, export-control entities, dual-use licenses & FTA origin rules. This page covers its hosted endpoint (https://api.mingxiapi.com/mcp).

Is the MingXi Export Control MCP server safe to use?

MingXi Export Control scores 62 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 MingXi Export Control MCP server expose?

MingXi Export Control exposes 6 tools: query_tariff, query_entity, query_dualuse, query_fta_origin, query_prohibited, query_any. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.

Does the MingXi Export Control MCP server require authentication?

No. We connected to MingXi Export Control without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MingXi Export Control MCP server still maintained?

MingXi Export Control is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.