# CN Evidence (remote · mcp.cnevidence.com)

China supplier checks via MCP/x402: Basic 0.032 USDC (3 modules); Full 0.093 USDC (9 modules).

- Trust score: 62/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mcp.cnevidence.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mikeyang7789-cn-evidence-mcp-public-cn-evidence/mcp.md), [page](https://verifymcp.io/servers/dev-workers-mikeyang7789-cn-evidence-mcp-public-cn-evidence/mcp)

## Channel facts

- Endpoint: `https://mcp.cnevidence.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-29.

- **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 call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 654 tokens (~218/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CN Evidence MCP server?

CN Evidence is a hosted endpoint at https://mcp.cnevidence.com/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 dev-workers-mikeyang7789-cn-evidence-mcp-public- 'https://mcp.cnevidence.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
      "url": "https://mcp.cnevidence.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
      "type": "http",
      "url": "https://mcp.cnevidence.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mikeyang7789-cn-evidence-mcp-public-]
url = "https://mcp.cnevidence.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
      "type": "remote",
      "url": "https://mcp.cnevidence.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mikeyang7789-cn-evidence-mcp-public- --url 'https://mcp.cnevidence.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mikeyang7789-cn-evidence-mcp-public-:
    url: "https://mcp.cnevidence.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
      "Transport": "http",
      "Url": "https://mcp.cnevidence.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mikeyang7789-cn-evidence-mcp-public- -t streamable-http -u 'https://mcp.cnevidence.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
      "type": "http",
      "url": "https://mcp.cnevidence.com/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-28 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 61, +1)

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

### 2026-09-25 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_china_supplier_evidence_full” rewrote its description, which is the text the model reads
- [security] Tool “get_china_supplier_evidence_basic” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 163 → 218

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

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_china_supplier_evidence_basic” rewrote its description, which is the text the model reads
- [security] Tool “get_china_supplier_evidence_full” rewrote its description, which is the text the model reads
- [security] Tool “resolve_china_company” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “resolve_china_company” added an optional parameter “uscc”
- [cosmetic] “resolve_china_company” made “company” optional

### 2026-09-21 (score 59, −3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “resolve_china_company” rewrote its description, which is the text the model reads
- [security] Tool “get_china_supplier_evidence_basic” rewrote its description, which is the text the model reads
- [security] Tool “get_china_supplier_evidence_full” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 33% → 0%
- [functional improvement] Schema quality: 119 → 82
- [cosmetic] “resolve_china_company” reworded the description of “company”

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

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

### 2026-09-17 (score 61, +1)

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

## MCP tools (3)

### `resolve_china_company` (~62 tokens)

Free local input preflight, NOT entity resolution. No registry lookup, translation or payment. Check a Chinese legal name or USCC and prepare request shapes; input_ready does not mean the identity is verified.

Input parameters:

- `company`
- `uscc`

### `get_china_supplier_evidence_basic` (~183 tokens)

0.032 USDC via x402 on Base. Company registration, operating abnormalities, administrative penalties. Page 1, up to 10 records per list. No safety guarantee. Requires an x402 v2 payment client, a funded Base USDC wallet and spending authorization; a plain MCP connection alone cannot purchase data. Use an exact Chinese legal name or USCC, not a guessed English-name match. Setup and free fictional sample: https://yangchunhong3000.github.io/cn-evidence-public-docs/buyer-guide.html Optional 24h report recovery requires a saved random 32-byte hex X-CN-Recovery-Token header on the paid request, then a free POST to https://api.cnevidence.com/free/cn/payment/recover. See guide; never automatically repay after a timeout.

Input parameters:

- `query` (required)

### `get_china_supplier_evidence_full` (~189 tokens)

0.093 USDC via x402 on Base. Nine supplier information modules; selected current status and first page up to 10 records per list. No historical expansion or automatic paging. Not complete due diligence. Requires an x402 v2 payment client, a funded Base USDC wallet and spending authorization; a plain MCP connection alone cannot purchase data. Use an exact Chinese legal name or USCC, not a guessed English-name match. Setup and free fictional sample: https://yangchunhong3000.github.io/cn-evidence-public-docs/buyer-guide.html Optional 24h report recovery requires a saved random 32-byte hex X-CN-Recovery-Token header on the paid request, then a free POST to https://api.cnevidence.com/free/cn/payment/recover. See guide; never automatically repay after a timeout.

Input parameters:

- `request` (required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mikeyang7789-cn-evidence-mcp-public-cn-evidence/mcp#diagnostics

## Score history

- 2026-09-29: 62
- 2026-09-28: 62
- 2026-09-27: 61
- 2026-09-26: 61
- 2026-09-25: 60
- 2026-09-24: 60
- 2026-09-23: 60
- 2026-09-22: 60
- 2026-09-21: 59
- 2026-09-20: 62
- 2026-09-19: 62
- 2026-09-18: 61
- 2026-09-17: 61
- 2026-09-16: 60
- 2026-09-15: 60
- 2026-09-14: 59
- 2026-09-13: 59
- 2026-09-12: 58

## Common questions

### What is the CN Evidence MCP server?

CN Evidence is an MCP server listed in the public MCP registry as dev.workers.mikeyang7789.cn-evidence-mcp-public/cn-evidence. China supplier checks via MCP/x402: Basic 0.032 USDC (3 modules); Full 0.093 USDC (9 modules). This page covers its hosted endpoint (https://mcp.cnevidence.com/mcp).

### Is the CN Evidence MCP server safe to use?

CN Evidence scores 62 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 CN Evidence MCP server expose?

CN Evidence exposes 3 tools: resolve_china_company, get_china_supplier_evidence_basic, get_china_supplier_evidence_full. Their descriptions and schemas cost roughly 434 tokens of context every time the server is loaded.

### Does the CN Evidence MCP server require authentication?

No. We connected to CN Evidence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CN Evidence MCP server still maintained?

CN Evidence is still listed as active in the MCP registry. We last reached this channel on 29 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://mcp.cnevidence.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mikeyang7789-cn-evidence-mcp-public-cn-evidence/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mikeyang7789-cn-evidence-mcp-public-cn-evidence/mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mikeyang7789-cn-evidence-mcp-public-cn-evidence/mcp