Home / MCP registry index / com.madecheck/madecheck
MadeCheck
com.madecheck/madecheck in the official MCP registry.
Endpoint https://mcp.madecheck.com/v1.
The registry describes it as: Free landed cost estimates and import requirements for US businesses buying from China.
We read its 27 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
estimate_landed_cost list_import_requirements lookup_factory create_order_pack add_order_pack_material answer_order_pack_lines get_order_pack list_order_packs sign_order_pack_lines revoke_signoff send_order_pack_to_factory mark_deposit_paid decline_order_pack cancel_order_pack post_order_pack_message list_order_pack_messages request_compliance_check accept_compliance_quote get_compliance_check list_compliance_checks start_document_upload finish_document_upload get_credit_balance get_buy_credits_link list_pending_actions decide_pending_action pay_style_topup
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-madecheck-madecheck)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.