# Verify China Supplier | Supplier Check (remote · x402-stable-door.lu7897859.workers.dev)

Verify a Chinese supplier before you pay: company identity, status, risk signals. x402 per call.

- Trust score: 18/100 (low)
- Change this week: −40
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `x402-stable-door.lu7897859.workers.dev`: 18/100 (this document), [markdown](https://verifymcp.io/servers/lu7897859-tech-china-sourcing-audit/x402-stable-door.md), [page](https://verifymcp.io/servers/lu7897859-tech-china-sourcing-audit/x402-stable-door)

## Channel facts

- Endpoint: `https://x402-stable-door.lu7897859.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 530, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 530.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Verify China Supplier | Supplier Check MCP server?

Verify China Supplier | Supplier Check is a hosted endpoint at https://x402-stable-door.lu7897859.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http lu7897859-tech-china-sourcing-audit 'https://x402-stable-door.lu7897859.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lu7897859-tech-china-sourcing-audit": {
      "url": "https://x402-stable-door.lu7897859.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lu7897859-tech-china-sourcing-audit": {
      "type": "http",
      "url": "https://x402-stable-door.lu7897859.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lu7897859-tech-china-sourcing-audit]
url = "https://x402-stable-door.lu7897859.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lu7897859-tech-china-sourcing-audit": {
      "type": "remote",
      "url": "https://x402-stable-door.lu7897859.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lu7897859-tech-china-sourcing-audit --url 'https://x402-stable-door.lu7897859.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lu7897859-tech-china-sourcing-audit:
    url: "https://x402-stable-door.lu7897859.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lu7897859-tech-china-sourcing-audit": {
      "Transport": "http",
      "Url": "https://x402-stable-door.lu7897859.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lu7897859-tech-china-sourcing-audit -t streamable-http -u 'https://x402-stable-door.lu7897859.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lu7897859-tech-china-sourcing-audit": {
      "type": "http",
      "url": "https://x402-stable-door.lu7897859.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 18, −42)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.33 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-19 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 59, +41)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] Schema quality: 130 → 147
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.30
- [functional improvement] MCP protocol: unverified → pass
- [functional] New tool “cpsc_recall_history”
- [functional] New tool “export_portrait_card”

### 2026-09-15 (score 18, −40)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.17 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-09-13 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 57, +39)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-11 (score 18, −38)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-10 (score 56, 0)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified

## MCP tools (8)

### `verify_supplier` (~150 tokens)

Verify Supplier

Verify whether a Chinese company is a REAL factory or a trading company/middleman.
Use when a buyer provides a Chinese company name, USCI, or a 1688/Alibaba vendor and needs hard fraud flags.
Checks public registry signals: shell-company traits, missing manufacturing scope in business license, low registered capital vs real factories (100万+), no factory evidence.
NOT for US/EU company verification (those jurisdictions use Middesk/VAT-style registries).
Provide company name and any known details (business scope, registered capital). Returns red flags to check and verification steps.

Input parameters:

- `business_scope` (string)
- `company_name` (string, required)
- `registered_capital` (string)

Output parameters:

- `result` (string)

### `landed_cost_calc` (~163 tokens)

Landed Cost Calc

Calculate true landed cost for China-to-US/EU imports: volumetric weight (air /6000, freight), destination port charges (CFS/doc fees), customs duty risk incl HS-code misclassification (12% error rate, 18-month retroactive).
Use before budgeting any import order to avoid 40-80% hidden overpayments on light bulky goods.
Input: weight (kg), dimensions (cm), goods value (USD), shipping mode (air/sea). Estimates only, not a customs quote.

Input parameters:

- `goods_value_usd` (number, required)
- `height_cm` (number, required)
- `length_cm` (number, required)
- `shipping_mode` (string)
- `weight_kg` (number, required)
- `width_cm` (number, required)

Output parameters:

- `result` (string)

### `payment_red_flags` (~133 tokens)

Payment Red Flags

Screen a Chinese supplier payment arrangement for wire-fraud red flags BEFORE sending a deposit.
Flags: personal-account payee (legit factories use corporate accounts), payee not matching contract party, urgent account changes (classic email-hijack fraud), deposit >30% above industry norm.
Returns go/no-go signals plus safe-payment rules. Use whenever a buyer is about to wire money to China.

Input parameters:

- `contract_ok` (boolean)
- `deposit_pct` (number)
- `pay_to_personal` (boolean)
- `payee_matches_contract` (boolean)
- `urgent_account_change` (boolean)

Output parameters:

- `result` (string)

### `audit_checklist` (~81 tokens)

Audit Checklist

Get the complete 7-point China sourcing audit checklist for first-time importers.
Covers: business-license verification, live factory video call, export records, sample sealing, safe payment, landed-cost buffer, certificate authenticity.
Use before sending any deposit to a new supplier. Based on 20 years of China manufacturing experience.

Input parameters:

- `use_case` (string)

Output parameters:

- `result` (string)

### `full_supplier_audit` (~152 tokens)

Full Supplier Audit

FULL-CHAIN supplier audit: one call runs the complete 5-stage pre-purchase decision (verify supplier -> landed cost -> payment red flags -> audit checklist -> certifications) and returns a unified risk verdict. The AI-commerce one-stop gate for buying from China. Cheaper than calling 5 tools separately; designed for agents that need a complete decision, not a single lookup.

Input parameters:

- `company_name` (string, required)
- `deposit_pct` (number)
- `goods_value_usd` (number)
- `height_cm` (number)
- `length_cm` (number)
- `shipping_mode` (string)
- `weight_kg` (number)
- `width_cm` (number)

Output parameters:

- `result` (string)

### `export_portrait_card` (~261 tokens)

Export Portrait Card

Draw a company's SELF-PORTRAIT CARD - a warm, appreciative one-page profile that shows a company
what the OTHER side of the border sees, praises its real strengths, and points out only the few gaps
that come from limited cross-market awareness. Two directions:
  direction="out" (default): a Chinese company going global - shows what OVERSEAS buyers see.
  direction="in": a foreign company entering China - shows what CHINESE partners see.
Designed to be GIFTED as a value-first approach: the card is about THEM, not our ad; free to receive,
so refusing requires an excuse. Use when an agent introduces a company across the China/global divide.

Tone contract (MUST follow): heavy praise grounded in facts; gaps framed ONLY as 'limited
cross-market awareness' - never capability, quality, or integrity. Never emit fraud/risk/red-flag words.

Input parameters:

- `company_name` (string, required)
- `direction` (string)
- `founded_year` (string)
- `has_english_site` (boolean)
- `is_listed` (boolean)
- `listing_code` (string)
- `recent_disclosures` (integer)
- `registered_capital` (string)

Output parameters:

- `result` (string)

### `certification_check` (~70 tokens)

Certification Check

Check which certifications (CE/FCC/FDA) a product type requires for EU/US import and how to verify certificate authenticity (issuer website lookup of cert numbers).
Use when unsure if a supplier's certificate is genuine — fake CE certificates are common and cause customs seizures.

Input parameters:

- `product_type` (string)

Output parameters:

- `result` (string)

### `cpsc_recall_history` (~137 tokens)

Cpsc Recall History

Check a Chinese factory's US product-recall history in the official CPSC SaferProducts recall database.
Use when a buyer wants evidence that a supplier really ships to the US (a recall record proves the company
sold under its own name into the US market) AND that it has a public safety record worth checking.
Source: US Consumer Product Safety Commission public recall REST service (free, no key). One-line verdict + citable evidence chain.
Disclaimer: not a legal opinion or credit report; 'not found' means not found in public CPSC data, not 'never recalled'.

Input parameters:

- `company_name` (string)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lu7897859-tech-china-sourcing-audit/x402-stable-door#diagnostics

## Score history

- 2026-09-21: 18
- 2026-09-20: 18
- 2026-09-19: 60
- 2026-09-18: 59
- 2026-09-17: 18
- 2026-09-16: 18
- 2026-09-15: 18
- 2026-09-14: 58
- 2026-09-13: 58
- 2026-09-12: 57
- 2026-09-11: 18
- 2026-09-10: 56
- 2026-09-09: 56

## Common questions

### What is the Verify China Supplier | Supplier Check MCP server?

Verify China Supplier | Supplier Check is an MCP server listed in the public MCP registry as io.github.lu7897859-tech/china-sourcing-audit. Verify a Chinese supplier before you pay: company identity, status, risk signals. x402 per call. This page covers its hosted endpoint (https://x402-stable-door.lu7897859.workers.dev/mcp).

### Is the Verify China Supplier | Supplier Check MCP server safe to use?

Verify China Supplier | Supplier Check scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Verify China Supplier | Supplier Check MCP server expose?

Verify China Supplier | Supplier Check exposes 8 tools: verify_supplier, landed_cost_calc, payment_red_flags, audit_checklist, full_supplier_audit, and 3 more. Their descriptions and schemas cost roughly 1,147 tokens of context every time the server is loaded.

### Does the Verify China Supplier | Supplier Check MCP server require authentication?

No. We connected to Verify China Supplier | Supplier Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Verify China Supplier | Supplier Check MCP server still maintained?

Verify China Supplier | Supplier Check is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://x402-stable-door.lu7897859.workers.dev/mcp
- Repository: https://github.com/lu7897859-tech/china-sourcing-audit
- Website: https://lu7897859-tech.github.io/doors/sourcing-audit/
- Changelog RSS feed: https://verifymcp.io/servers/lu7897859-tech-china-sourcing-audit/x402-stable-door.xml
- Changelog JSON feed: https://verifymcp.io/servers/lu7897859-tech-china-sourcing-audit/x402-stable-door.json
- HTML version of this page: https://verifymcp.io/servers/lu7897859-tech-china-sourcing-audit/x402-stable-door