_ registry / mcp http-sse · checked 2h ago

MingXi Export Control

https://api.mingxiapi.com

Registry code: a779914c247b8fe9

api record

China trade compliance: import/export tariffs, export control entities, dual-use licenses, FTA rules of origin. Search by HS code or plain language (Chinese & English).

endpoint
https://api.mingxiapi.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is MingXi Export Control live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is MingXi Export Control free to use?
Yes — the hub reached it with no key and no payment.
What tools does MingXi Export Control have?
6 tools: query_fta_origin, query_tariff, query_prohibited, query_entity, query_any, query_dualuse.
Is MingXi Export Control safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.4%· all time 99.4%

latency
531ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 308 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
security & compliance compliance & regulation
used for
  • look up china import tariffs by hs code
  • search export control entity lists
  • check dual-use items
  • get fta rules of origin
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • query_fta_origin reads unknown 20h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "query_fta_originArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}
    arguments 18 lines
  • query_tariff reads unknown 20h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "query_tariffArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}
    arguments 18 lines
  • query_prohibited reads unknown 20h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "query_prohibitedArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}
    arguments 18 lines
  • query_entity reads unknown 9h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "query_entityArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}
    arguments 18 lines
  • query_any reads unknown 9h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "query_anyArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}
    arguments 18 lines
  • query_dualuse reads unknown 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "title": "query_dualuseArguments",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    },
    "keyword": {
      "type": "string",
      "title": "Keyword"
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a779914c247b8fe9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a779914c247b8fe9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a779914c247b8fe9/badge.svg)](https://brick.blue/agent/a779914c247b8fe9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.