CN Evidence
REMOTE · MCP.CNEVIDENCE.COM · SCANNED SEP 29
China supplier checks via MCP/x402: Basic 0.032 USDC (3 modules); Full 0.093 USDC (9 modules).
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.cnevidence.com
claude mcp add --transport http dev-workers-mikeyang7789-cn-evidence-mcp-public- 'https://mcp.cnevidence.com/mcp'
{
"mcpServers": {
"dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
"url": "https://mcp.cnevidence.com/mcp"
}
}
} {
"servers": {
"dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
"type": "http",
"url": "https://mcp.cnevidence.com/mcp"
}
}
} [mcp_servers.dev-workers-mikeyang7789-cn-evidence-mcp-public-] url = "https://mcp.cnevidence.com/mcp"
{
"$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 mcp add dev-workers-mikeyang7789-cn-evidence-mcp-public- --url 'https://mcp.cnevidence.com/mcp' --transport streamable-http
mcp_servers:
dev-workers-mikeyang7789-cn-evidence-mcp-public-:
url: "https://mcp.cnevidence.com/mcp" {
"McpServers": {
"dev-workers-mikeyang7789-cn-evidence-mcp-public-": {
"Transport": "http",
"Url": "https://mcp.cnevidence.com/mcp"
}
}
} assistant mcp add dev-workers-mikeyang7789-cn-evidence-mcp-public- -t streamable-http -u 'https://mcp.cnevidence.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- 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 security
- Schema quality: 163 → 218 ▼ functional
- 22 Sept 26 +1
- 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 security
- Schema quality: pass → fail ▼ functional
- “resolve_china_company” added an optional parameter “uscc” cosmetic
- “resolve_china_company” made “company” optional cosmetic
- 21 Sept 26 −3
- 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 security
- Tool coverage: 33% → 0% ▼ functional
- Schema quality: 119 → 82 ▲ functional
- “resolve_china_company” reworded the description of “company” cosmetic
- 19 Sept 26 +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.
- 17 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://mcp.cnevidence.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cnevidence.com | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 617d41584151c4fc13be33dba0eab0bc |
| SANs: cnevidence.com, mcp.cnevidence.com, *.mcp.cnevidence.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cnevidence.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cnevidence.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cnevidence.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cnevidence.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_china_supplier_evidence_basic ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | – | yes | – |
No output schema declared.
No examples provided.
get_china_supplier_evidence_full ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request | – | yes | – |
No output schema declared.
No examples provided.
resolve_china_company ~62
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | – |
| uscc | – | – | – |
No output schema declared.
No examples provided.
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.