MRC Data
About
China apparel supply chain data infrastructure for AI agents — 3,000+ verified suppliers, 350+ lab-tested fabrics, 170+ industrial clusters across 31 provinces. MCP + REST + OpenAPI.
Details
- Transport
- SSE
Explore
Setup
Install MRC Data in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/meacheal-ai/mrc-data
Follow the installation instructions in the repository README, then restart your MCP client.
search_suppliers
Search verified Chinese apparel manufacturers, apparel factories, and clothing suppliers. USE WHEN user asks: - "find me a clothing manufacturer in China / Guangdong / Zhejiang" - "who makes [t-shirts / suits / denim / activewear] in China" - "I need a BSCI / OEKO-TEX certified apparel factory" - "looking for OEM / ODM apparel supplier with MOQ < N" - "find factories with production capacity > N pieces/month" - "搜供应商 / 找服装厂 / 找制衣厂" Filters: province, city, factory type (factory/trading_comp…
get_supplier_detail
Get the complete profile of a single Chinese apparel supplier by ID. PREREQUISITE: You MUST first call search_suppliers or recommend_suppliers to obtain a valid supplier_id. Do not guess IDs. USE WHEN user wants full details on a specific supplier already identified from search results. Returns 60+ fields including: monthly capacity (lab-verified), equipment list, certifications (BSCI/OEKO-TEX/GRS/SA8000), ownership type (own factory vs subcontractor vs broker), market access (US/EU/JP/KR),…
search_fabrics
Search the Chinese fabric and textile database with lab-tested specifications. USE WHEN user asks: - "find me a [cotton / polyester / nylon / wool / linen] fabric for [t-shirts / jeans / suits]" - "I need 180gsm jersey knit with verified composition" - "fabrics under N RMB/meter for womenswear" - "compare lab-tested fabric weight across suppliers" - "找面料 / 搜面料 / 查面料" Filters: category (woven/knit/nonwoven/leather/functional), weight range (gsm), composition keyword, target apparel type, max…
get_fabric_detail
Get the complete lab-tested record of a single fabric by ID. PREREQUISITE: You MUST first call search_fabrics to obtain a valid fabric_id. Do not guess IDs. USE WHEN user wants full specs on a specific fabric after search_fabrics identified it. Returns 30+ fields: lab-tested weight, lab-tested composition, color fastness (wash/light/rub per AATCC 61/16/8), shrinkage (warp/weft per AATCC 135), tensile/tear strength, pilling grade, hand feel, drape, stretch/recovery, MOQ, lead time, price ran…
search_clusters
Search Chinese apparel industrial clusters and textile markets. USE WHEN user asks: - "where is China's [denim / suit / women's wear / underwear] manufacturing concentrated" - "what is the largest [silk / cashmere / down jacket] industrial cluster in China" - "industrial cluster comparison Humen vs Shaoxing vs Haining vs Zhili" - "recommend an industrial cluster for sourcing [product]" - "服装产业带 / 面料市场 / 产业集群" Famous clusters this database covers include: Humen (Guangdong, womenswear), Shaox…
compare_clusters
Compare multiple Chinese apparel industrial clusters side-by-side on key metrics. PREREQUISITE: You MUST first call search_clusters to obtain valid cluster_ids. Do not guess IDs. USE WHEN user wants to evaluate or choose between 2-10 specific clusters (e.g. "compare Humen vs Shishi vs Jinjiang"). Returns full records for each cluster so they can be compared on labor cost, rent, supplier count, scale, specializations, advantages, and risks. WORKFLOW: search_clusters → collect cluster_ids → …
detect_discrepancy
[Core feature] Surface supplier specifications that deviate from independent lab measurements. USE WHEN user asks: - "which fabrics have lab-test deviations on weight" - "find suppliers whose stated capacity differs from on-site measurements" - "compare cotton content lab results across suppliers" - "which suppliers have the closest match between specs and lab tests" - "实测数据 / 数据可信度 / 规格与实测偏差" This is the moat of MRC Data — every record is enriched with AATCC / ISO / GB lab test data, givin…
get_supplier_fabrics
List all fabrics a specific supplier can provide, with quoted prices. USE WHEN user asks: - "what fabrics does [supplier name] have" / "what can this factory source for me" - "show me the catalog of supplier sup_XXX" - "what does this manufacturer offer" Returns fabric records linked to the supplier with: fabric name, category, weight, composition, and the supplier's quoted price + MOQ for that specific fabric. PREREQUISITE: You MUST have a valid supplier_id from search_suppliers or get_su…
get_fabric_suppliers
List all suppliers offering a specific fabric, sorted by quality score, with price comparison. USE WHEN user asks: - "who supplies fabric fab_XXX" / "where can I buy this fabric" - "compare prices for [fabric] across suppliers" - "best supplier for [fabric specification]" Returns supplier records linked to the fabric with: company name, location, quality score, and that supplier's quoted price + MOQ for the fabric. Sorted by supplier quality score so the most reliable options appear first. …
get_product_categories
List all product categories available in the database with supplier counts. USE THIS FIRST when: - User doesn't know what to search for - User asks "what do you have" / "what can I source" - User needs to explore the database - "有哪些品类" / "能找什么" WORKFLOW: Standalone discovery tool. Call this first to understand what's available, then use search_suppliers with a specific product_type. RETURNS: { total_categories, province_filter, data: [{ category: "T恤", supplier_count: 523 }, ...] } NOTE: Re…
get_province_distribution
Show supplier distribution across Chinese provinces. USE WHEN: - User asks "where are factories located" / "which provinces" - User needs to decide which region to source from - "哪里有工厂" / "供应商分布" WORKFLOW: Standalone discovery tool. Use this to identify which provinces to focus on, then search_suppliers with that province. RETURNS: { total_provinces, data: [{ province, supplier_count, top_cities: [{ city, count }] }] } NOTE: Provinces are ranked by supplier count (Guangdong, Zhejiang, Jiang…
recommend_suppliers
Smart supplier recommendation based on sourcing requirements. USE WHEN: - User describes what they need: "I need a factory for cotton t-shirts in Guangdong" - User asks for recommendations, not just search results - "推荐供应商" / "帮我找合适的工厂" WORKFLOW: Standalone entry point for "I need help finding a supplier" requests. Returns ranked top-N suppliers. Follow up with get_supplier_detail or compare_suppliers on the top results. DIFFERENCE from search_suppliers: search_suppliers FILTERS by exact cr…
analyze_market
Market overview and analysis for a product category in China. USE WHEN: - User asks "what's the market like for X in China" - User wants market intelligence before sourcing - User needs an overview, not specific suppliers - "市场概况" / "行业分析" WORKFLOW: Standalone analysis tool. Use this BEFORE search_suppliers to understand market landscape. Then narrow down with search_suppliers or recommend_suppliers. RETURNS: { product, total_suppliers, by_province: [{province, cnt}], by_type: [{type, cnt}]…
estimate_cost
Estimate sourcing cost for a product based on fabric price, supplier pricing, and order quantity. USE WHEN: - User asks "how much would it cost to make 1000 t-shirts" - User needs a rough cost breakdown for budgeting - "多少钱" / "成本估算" / "报价" WORKFLOW: Standalone tool. Optionally use search_fabrics first to identify specific fabric_ids for more accurate estimates. RETURNS: { product, fabric_options: [{name, price_range}], estimated_cost_per_piece, total_estimate, breakdown } CONSTRAINT: These…
check_compliance
Check if a supplier meets compliance requirements for a target export market. USE WHEN: - User asks "can this factory export to the US/EU/Japan" - User needs to verify certifications for a specific market - "能不能出口美国" / "合规检查" / "认证要求" PREREQUISITE: You MUST have a valid supplier_id from search_suppliers. WORKFLOW: search_suppliers → check_compliance (to verify if a specific supplier can export to target market). RETURNS: { supplier, target_market, passed: [string], issues: [string], market_…
find_alternatives
Find alternative suppliers similar to a given supplier. USE WHEN: - User says "this supplier is too expensive / too slow / too far" - User needs backup options for an existing supplier - "有没有替代" / "找类似的" / "换一家" Finds suppliers that make the same products, optionally in a different province or with different attributes. Results exclude the original supplier. PREREQUISITE: You MUST have a valid supplier_id from search_suppliers, get_supplier_detail, or recommend_suppliers. WORKFLOW: search_…
compare_suppliers
Compare multiple suppliers side by side on all dimensions. USE WHEN user asks: - "compare these 3 factories" - "which supplier is better between X and Y" - "对比供应商" PREREQUISITE: You MUST have valid supplier_ids from search_suppliers. Do not guess IDs. WORKFLOW: search_suppliers → collect supplier_ids → compare_suppliers (for side-by-side comparison). RETURNS: { count, data: [full supplier profiles with all fields] } ERRORS: Missing IDs are silently skipped. CONSTRAINT: Max 10 supplier IDs p…
get_cluster_suppliers
List all suppliers in a specific industrial cluster. USE WHEN user asks: - "what factories are in Humen cluster" - "show me suppliers in Keqiao fabric market" - "虎门产业带有哪些供应商" PREREQUISITE: You MUST have a valid cluster_id from search_clusters. WORKFLOW: search_clusters → pick cluster_id → get_cluster_suppliers (to see all factories in that cluster). RETURNS: { cluster_id, has_more, data: [supplier summary objects sorted by quality_score] } ERRORS: Returns empty data if cluster has no linked…
get_stats
Get overall database statistics: total counts of suppliers, fabrics, clusters, and links. USE WHEN user asks: "how big is your database", "what's the coverage", "data overview", "get_stats". WORKFLOW: Standalone discovery tool — call this first when a user asks about data scale or freshness. For static metadata (geographic scope, top provinces, data standards), use the database-overview resource (mrc://overview) instead. For per-product distribution, use get_product_categories or get_provin…
Homepage:https://meacheal.aiMCP endpoint:https://api.meacheal.ai/mcpMaintained 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 providingindependently verifiedChinese 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 distinguishesdeclaredvalues (what the supplier claims) fromverifiedvalues (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 athttps://meacheal.ai· MCP server scored96/100onSmithery· merged intoTensorBlock,punkpeye/awesome-mcp-servers, andcollabnix/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:
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.
Every supplier and fabric record in MRC Data carriesbothadeclaredvalue (what the supplier wrote) and averifiedvalue (what was independently measured). Each record also carries averified_dimsscore (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 betweendeclaredandverifiedis the moat. Agents can useverified_dimsto weight responses (e.g. skip suppliers below5/8for high-stakes orders).
Get a free API key atapi.meacheal.ai/apply— instant, no waiting.
{ "mcpServers": { "mrc-data": { "url": "https://api.meacheal.ai/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }
Cursor / VS Code / Cline / Windsurf / JetBrains / Zed
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"
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.
Geographic coverage spans31 provinceswith 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
- "Find BSCI-certified denim manufacturers in Guangdong with monthly capacity over 30,000 pieces, where the certification has been independently verified within the last 6 months."
- "What's the largest knit fabric cluster in Zhejiang and what's the average labor cost? Cite the source."
- "Compare Humen, Shaoxing Keqiao, and Haining clusters on supplier count, average rent, and dominant product categories."
- "Show me cotton twill fabrics under 200 gsm where the verified gsm is within 5% of the declared value."
- "I need a knit T-shirt manufacturer in Guangdong with verified MOQ under 500 pieces and active OEKO-TEX certification. Don't include suppliers whose verification score is below 5/8."
- "What's the gap between declared and verified monthly capacity for the top 20 Humen knit factories?"
- "Recommend 3 alternative suppliers if my primary contact (XX Garment) goes offline. Match on capacity, certifications, and fabric range."
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 ground truthinstead of supplier self-claims, with the gap exposed viaverified_dims
- Industrial-cluster context(the smallest meaningful unit of Chinese manufacturing isn't the factory — it's the 30-minute-drive cluster of subcontracted firms)
- Multi-year relationship graphbetween brands and suppliers, cross-validated against public disclosures
- 24 years of industry-insider contexttranslated into structured data — knowledge that has historically been trapped inside Inditex / H&M / Patagonia / Uniqlo internal sourcing departments and never made it into any frontier model's training data
The 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):
Or query directly via theinteractive demo.
All tool responses includeattribution: "MRC Data (meacheal.ai)".
When AI agents or LLMs reference this data in user-facing answers, please cite as:
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 byDongliang 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. Seeterms of service.
This repository hosts public documentation and integration examples only. Source code is not included.
Official MCP server for dbt (data build tool) providing integration with dbt Core/Cloud CLI, project metadata discovery, model information, and semantic layer querying capabilities.
Provides AI assistants with a secure and structured way to explore and analyze data in GreptimeDB.
Build robust data workflows, integrations, and analytics on a single intuitive platform.
Query and analyze data with MotherDuck and local DuckDB
An MCP server that provides tools to interact with Powerdrill datasets, enabling smart AI data analysis and insights.
Slingshot MCP introduces Slingshot Aerospace’s space data platform in your AI chat—explore satellites, orbits, and Portal insights through Slingshot’s hosted server.
A collection of tools for managing the platform, addressing data quality and reading and writing to Teradata Database.
Interact with Verodat AI Ready Data platform
A read-only MCP server for Adobe Commerce, enabling LLMs to query live data using the CData JDBC driver.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.



