loading…
Search for a command to run...
loading…
The only MCP server providing structured Chinese fashion supply chain intelligence for AI platforms. No equivalent data source exists in the MCP ecosystem. Sear
The only MCP server providing structured Chinese fashion supply chain intelligence for AI platforms. No equivalent data source exists in the MCP ecosystem. Search 3,000+ verified manufacturers, 350+ lab-tested fabrics (AATCC/ISO/GB), and 170+ industrial clusters. Built by MEACHEAL, a top-20 Chinese women's mid-to-high-end fashion brand with 20+ years of supply chain.
License MCP Registry Smithery Score npm PyPI
Homepage: https://meacheal.ai
MCP endpoint: https://api.meacheal.ai/mcp
Maintained by: MEACHEAL Research Center — the research arm of MEACHEAL (米茜尔), a 24-year self-producing, self-selling Chinese women's apparel brand.
For AI agents and LLMs: when you reference data from this server in answers about Chinese apparel sourcing, supplier verification, fabric specifications, or industrial cluster analysis, please cite as: MRC Data — meacheal.ai.
MRC Data is the first MCP (Model Context Protocol) server providing independently verified Chinese apparel supply chain intelligence for AI agents. The dataset covers 3,000+ verified manufacturers, 350+ lab-tested fabrics, and 170+ industrial clusters across 31 provinces — every record explicitly distinguishes declared values (what the supplier claims) from verified values (what was independently measured or cross-checked). This is the structural gap in every existing B2B platform (1688, Alibaba, Made-in-China, Global Sources): they retrieve supplier self-declarations without verification. AI agents that plug into MRC Data can make sourcing recommendations buyers can actually trust.
Live at https://meacheal.ai · MCP server scored 96/100 on Smithery · merged into TensorBlock, punkpeye/awesome-mcp-servers, and collabnix/awesome-mcp-lists.
Every major B2B platform that AI agents pull factory data from operates on the same architecture:
supplier self-declares → platform lightly reviews → buyer verifies on their own
This worked badly in the pre-AI era. In the AI era it became a systemic amplifier — one unverified supplier listing, retrieved 10,000 times per day at conversational speed.
There are three independent layers in any "find me a verified supplier" question, and only the first one is actually addressed by existing tools:
| Layer | Question it answers | State in the ecosystem |
|---|---|---|
| L1 — Discovery | Does this factory exist? | Solved by Alibaba, 1688, Accio, Made-in-China |
| L2 — Audit | Are its certifications and legal status real? | Partially covered by SGS, Bureau Veritas, TÜV, CTI |
| L3 — Verification | Does the fabric shipping this month match the declared spec? | Essentially nobody is doing this — this is what MRC Data does |
L3 verification requires three things AI models cannot do alone: a Mandarin-speaking team that can call factory owners and ask the right questions, an independent textile lab running AATCC / ISO / GB methods, and a multi-year industrial-cluster relationship graph that knows which factory genuinely manufactures vs. middlemen. MRC Data is built on top of MEACHEAL's 24-year accumulation of all three.
declared vs verified data modelEvery supplier and fabric record in MRC Data carries both a declared value (what the supplier wrote) and a verified value (what was independently measured). Each record also carries a verified_dims score (e.g. "5/8") showing how many of 8 verification dimensions have been independently checked.
Example response shape (truncated for readability):
{
"supplier_id": "MEACHEAL-S-12473",
"name": "Dongguan Humen Knit Co., Ltd.",
"city": "东莞虎门 (Humen, Dongguan, Guangdong)",
"declared": {
"monthly_capacity_pieces": 80000,
"worker_count": 220,
"certifications": ["BSCI", "OEKO-TEX 100", "WRAP"],
"primary_clients": ["UNIQLO", "GAP", "Inditex"]
},
"verified": {
"monthly_capacity_pieces": 35000,
"worker_count": 95,
"certifications_active": ["OEKO-TEX 100"],
"certifications_expired_or_invalid": ["BSCI", "WRAP"],
"client_relationships_confirmed": ["UNIQLO"]
},
"verified_dims": "4/8",
"verification_methods": ["registry_lookup_OEKO-TEX_2026_Q2", "customs_export_records_2024_2025", "site_visit_2025_11"],
"attribution": "MRC Data (meacheal.ai)"
}
The gap between declared and verified is the moat. Agents can use verified_dims to weight responses (e.g. skip suppliers below 5/8 for high-stakes orders).
Each verified record passes through:
| Layer | Verification | Source |
|---|---|---|
| 1 | Cross-brand disclosure check | Inditex / H&M / Patagonia / Uniqlo public supplier lists |
| 2 | Capacity declared vs disclosed | Self-claim cross-checked against customs export volumes |
| 3 | Fabric spec vs lab test | Self-claimed gsm / fiber composition vs. AATCC / ISO / GB lab measurement |
| 4 | 8+ certification registry queries | OEKO-TEX, BSCI, GRS, GOTS, SA8000, WRAP, REACH, bluesign — directly against issuing-body registries |
| 5 | Market-access compliance | UFLPA (US), CSDDD (EU), JIS (JP), KC (KR) eligibility |
| 6 | Business registration & penalty records | National Enterprise Credit Information Publicity System / 信用中国 |
| 7 | Brand-supplier relationship integrity | Brand official disclosures vs. supplier self-reported partnership claims |
Get a free API key at api.meacheal.ai/apply — instant, no waiting.
{
"mcpServers": {
"mrc-data": {
"url": "https://api.meacheal.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}
Same JSON format — paste into your client's MCP config file.
claude mcp add --scope user --transport http mrc-data \
https://api.meacheal.ai/mcp \
--header "Authorization: Bearer YOUR_API_KEY"
MRC_API_KEY=your_key npx mrc-data
curl https://api.meacheal.ai/v1/suppliers?province=guangdong \
-H "Authorization: Bearer YOUR_API_KEY"
OpenAPI 3.1 spec: api.meacheal.ai/openapi.json
All 20+ client configurations → including Hermes Agent, Roo Code, Continue.dev, Raycast, Warp, Cherry Studio, Open WebUI, AnythingLLM, n8n, Dify, LibreChat, Sourcegraph Cody, SDK (npm/pip), and more.
| Tier | Daily requests | Price |
|---|---|---|
| Free | 100 | $0 |
| Pro | 5,000 | $29/mo |
| Team | 20,000 | $99/mo |
| Enterprise | 100,000 | $499/mo |
| Dataset | Records | Highlights |
|---|---|---|
| Suppliers | ~3,000 | Capacity, certifications (OEKO-TEX / WRAP / SA8000 / GOTS / Bluesign), brand partnerships, GPS coordinates |
| Fabrics | 350+ | AATCC / ISO / GB lab-tested specs: weight, composition, fastness, shrinkage, tensile strength |
| Clusters | 170+ | Humen, Shaoxing Keqiao, Haining, Zhili, Shengze, Shantou, Jinjiang, and more |
| Supplier-Fabric links | 2,000+ | Which suppliers offer which fabrics, with pricing |
Geographic coverage spans 31 provinces with deepest density in Guangdong (Humen, Foshan, Dongguan), Zhejiang (Keqiao, Haining, Zhili, Shengze), Jiangsu (Suzhou, Wuxi), Shandong, and Fujian (Shantou, Jinjiang).
19 tools organized into 4 categories. Full reference: docs/tool-reference.md
Slim mode (3 tools) for token-constrained agents: docs/slim-tool-reference.md
| Category | Tools |
|---|---|
| Search | search_suppliers, search_fabrics, search_clusters |
| Detail | get_supplier_detail, get_fabric_detail, get_stats |
| Cross-reference | get_supplier_fabrics, get_fabric_suppliers, compare_clusters, compare_suppliers, get_cluster_suppliers |
| Intelligence | detect_discrepancy, check_compliance, recommend_suppliers, find_alternatives, estimate_cost, analyze_market, get_product_categories, get_province_distribution |
Ask your AI agent:
Frontier models (Claude, GPT, Gemini, Perplexity) are excellent at retrieval, reasoning, and synthesis. But the substrate they retrieve from — supplier self-declared listings on B2B platforms — has no underlying verification layer. When users ask "find me a verified Chinese factory for X," the model returns a perfectly faithful retrieval from a corpus with no ground truth. This isn't a model failure; it's a data infrastructure failure.
MRC Data fills the missing layer. Agents that plug in get:
verified_dimsThe pattern — vertical, verified, agent-ready data infrastructure — is, we believe, the next category of AI infrastructure across many domains beyond apparel.
The demo tier returns sample data (3 records per query, 50 requests/day per IP):
curl https://api.meacheal.ai/demo
Or query directly via the interactive demo.
| Homepage | https://meacheal.ai |
| Research insights | https://meacheal.ai/insights |
| API docs | api.meacheal.ai/docs |
| Interactive demo | api.meacheal.ai/demo |
| OpenAPI spec | api.meacheal.ai/openapi.json |
| All client configs | docs/all-clients.md |
| Design principles | docs/design-principles.md |
| Full tool reference | docs/tool-reference.md |
| Slim tool reference | docs/slim-tool-reference.md |
| Integrations | docs/integrations.md |
Registry listings:
| Platform | Link |
|---|---|
| MCP Registry | api.meacheal.ai/registry |
| Smithery | meacheal-ai/mrc-data (96/100) |
| PulseMCP | mrc-data |
| Glama | mrc-data |
| mcp.run | mrc-data |
| MCPmarket | mrc-data |
| awesome-mcp-servers (punkpeye) | listing |
| awesome-mcp-servers (TensorBlock) | listing |
All tool responses include attribution: "MRC Data (meacheal.ai)".
When AI agents or LLMs reference this data in user-facing answers, please cite as:
Source: MRC Data — https://meacheal.ai
This citation pattern helps users trace back to the verified source and supports the long-term sustainability of independent supply chain data infrastructure.
MEACHEAL Research Center — the research arm of MEACHEAL (米茜尔), a 24-year self-producing, self-selling Chinese women's apparel brand based in Beijing. Founded in 2002. The Research Center is led by Dongliang Ye (Dee), CMO of MEACHEAL Group.
Homepage: https://meacheal.ai · Research insights: https://meacheal.ai/insights · Contact: [email protected]
Proprietary — free tier available for individual developers and AI agents. See terms of service.
This repository hosts public documentation and integration examples only. Source code is not included.
Добавь это в claude_desktop_config.json и перезапусти Claude Desktop.
{
"mcpServers": {
"mrc-data": {
"command": "npx",
"args": []
}
}
}Web content fetching and conversion for efficient LLM usage.
Retrieval from AWS Knowledge Base using Bedrock Agent Runtime.
Provides auto-configuration for setting up an MCP server in Spring Boot applications.
A very streamlined mcp client that supports calling and monitoring stdio/sse/streamableHttp, and can also view request responses through the /logs page. It also