Skip to content

MadeCheck

Estimates landed costs and lists import requirements for small goods bought from China, served to your AI assistant through an MCP endpoint.
MadeCheck: data, price, alternatives
At a glancechecked Oct 24, 2026

not read yet

Use

For
one-person businesses preparing to buy small goods from China
Used for
  • estimate landed cost of goods imported from China
  • check import requirements for a product before buying
Worth knowingcomputed from what we read · each with its source
  • Has an MCP server (1 in the registry)public registry →
How a program reaches itfound, not claimed · read Oct 28, 2026
  • MCP servercom.madecheck/madecheckverified in the MCP registry
  • Stateanswers, 28 toolschecked 2026-10-28
  • Address to connectmcp.madecheck.com/v1
  • OpenAPI spec25 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Commerceby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare MadeCheck with

Pick up to two.

All 10 alternatives to MadeCheck →

All Commerce tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use MadeCheck for?

Sign in to leave a note
Questions this page answers
  • What is MadeCheck?

    Estimates landed costs and lists import requirements for small goods bought from China, served to your AI assistant through an MCP endpoint. It is listed in the Atlas under Commerce.

  • Who is MadeCheck for?

    one-person businesses preparing to buy small goods from China

  • Do people use MadeCheck?

    Little sign of use.

  • What are alternatives to MadeCheck?

    In Commerce, by use: Unstoppable, Plati.Market, Seller Assistant, SMKlog, MoneyDeals.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk