search_suppliersLABSCO SUMMARY
The gap between declared and verified is the whole product.
Discovery-only supplier data is easy to come by; what is scarce is a second, independently measured number next to the claim, and that is what these records carry. The verified_dims score is the field to build on — an agent can be told to skip anything below a threshold rather than treating every listing as equally solid. Pricing is per-day request quota, so plan bulk comparison work around the tier you are on.
What it is
A hosted MCP server over a Chinese apparel supply-chain dataset: roughly 3,000 manufacturers, 350+ lab-tested fabrics and 170+ industrial clusters across 31 provinces. Every supplier and fabric record carries both what the supplier declared and what was independently measured, plus a verified_dims score showing how many of eight verification dimensions have been checked.
What you get
- Three search tools that filter without a lookup table —
search_suppliersby province, type, capacity, compliance status and quality score;search_fabricsby category, weight in gsm, composition and price;search_clustersby province, specialization and scale - Full records on demand:
get_supplier_detailandget_fabric_detailreturn the complete profile including lab measurements, certifications and market access - Cross-references that answer follow-up questions in one call —
get_supplier_fabrics,get_fabric_suppliers,get_cluster_suppliers, pluscompare_suppliersandcompare_clustersfor side-by-side reads detect_discrepancy, which surfaces exactly where a declared value diverges from the tested one, sorted by the size of the gap- Sourcing help rather than raw rows:
recommend_suppliers,find_alternatives,check_complianceagainst a target export market,estimate_costandanalyze_market - A slim mode of three tools —
search_suppliers,search_fabricsandget_stats— for agents on a tight context budget
Requirements
A free API key from the vendor's apply page, sent as a bearer token. The primary route is the hosted endpoint https://api.meacheal.ai/mcp over Streamable HTTP, pasted into any client's MCP config with an Authorization header; claude mcp add --transport http does the same in one command. An npm launcher also exists — npx mrc-data with MRC_API_KEY set — and the same data is available over a REST API with an OpenAPI 3.1 spec. The free tier allows 100 requests per day.
Setup effort
One command plus a key — MRC_API_KEY=<YOUR_MRC_API_KEY> npx mrc-data
USE CASES
Shortlisting factories you can defend to a buyer
Filter on capacity, certification and quality, then read the verification score before the shortlist goes anywhere.
Catching an inflated capacity claim
Ask for the records where the declared figure diverges most from the measured one, sorted by the size of the gap.
Matching a fabric to a garment before sampling
Filter on weight, composition and price, then read the lab-tested specification rather than the spec sheet.
Choosing between manufacturing clusters
Compare clusters on supplier count, labour cost and specialization in one call instead of assembling it by hand.
Checking a supplier against an export market
Ask whether a given supplier meets the requirements for the market you intend to ship to.
19 tools
Listed in project docs. Your client may show a different list.
search_fabricssearch_clustersget_supplier_detailget_fabric_detailget_statsget_supplier_fabricsget_fabric_supplierscompare_clusterscompare_suppliersget_cluster_suppliersdetect_discrepancycheck_compliancerecommend_suppliersfind_alternativesestimate_costanalyze_marketget_product_categoriesget_province_distributionBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
Requires
- A client that can reach a remote MCP server over HTTP
- MRC_API_KEY in your environment
Where it runs
Of the 9 documented clients, 1 runs the server on your machine and 8 connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
The install command the project publishes
MRC_API_KEY=<YOUR_MRC_API_KEY> npx mrc-dataHosted endpoint
https://api.meacheal.ai/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Cursor — HTTP, JetBrains IDEs — HTTP
{
"mcpServers": {
"mrc-data": {
"url": "https://api.meacheal.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MRC_API_KEY>"
}
}
}
}Cline — HTTP
{
"mcpServers": {
"mrc-data": {
"type": "streamableHttp",
"url": "https://api.meacheal.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MRC_API_KEY>"
}
}
}
}Claude Desktop — npx
{
"mcpServers": {
"mrc-data": {
"command": "npx",
"args": [
"-y",
"mrc-data"
],
"env": {
"MRC_API_KEY": "<YOUR_MRC_API_KEY>"
}
}
}
}Claude Code
claude mcp add --scope user --transport http mrc-data https://api.meacheal.ai/mcp --header "Authorization: Bearer <YOUR_MRC_API_KEY>"VS Code
{
"servers": {
"mrc-data": {
"type": "http",
"url": "https://api.meacheal.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MRC_API_KEY>"
}
}
}
}Windsurf
{
"mcpServers": {
"mrc-data": {
"serverUrl": "https://api.meacheal.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MRC_API_KEY>"
}
}
}
}Zed
{
"context_servers": {
"mrc-data": {
"url": "https://api.meacheal.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MRC_API_KEY>"
}
}
}
}Sourcegraph Cody
{
"cody.mcpServers": {
"mrc-data": {
"type": "streamable-http",
"url": "https://api.meacheal.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MRC_API_KEY>"
}
}
}
}