io.github.wangjingjing1026uwh-hub/zaoqiniaoer
REMOTE · ZAOQINIAOERHANNILE.COM · SCANNED SEP 29
Send three unrelated real people to a physical address in China and get back what they actually saw.
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 Security57
- 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 2 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 382 tokens (~191/item across 2 items; 2 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server?
io.github.wangjingjing1026uwh-hub/zaoqiniaoer is a hosted endpoint at https://zaoqiniaoerhannile.com/api/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 · zaoqiniaoerhannile.com
claude mcp add --transport http wangjingjing1026uwh-hub-zaoqiniaoer 'https://zaoqiniaoerhannile.com/api/mcp'
{
"mcpServers": {
"wangjingjing1026uwh-hub-zaoqiniaoer": {
"url": "https://zaoqiniaoerhannile.com/api/mcp"
}
}
} {
"servers": {
"wangjingjing1026uwh-hub-zaoqiniaoer": {
"type": "http",
"url": "https://zaoqiniaoerhannile.com/api/mcp"
}
}
} [mcp_servers.wangjingjing1026uwh-hub-zaoqiniaoer] url = "https://zaoqiniaoerhannile.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wangjingjing1026uwh-hub-zaoqiniaoer": {
"type": "remote",
"url": "https://zaoqiniaoerhannile.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add wangjingjing1026uwh-hub-zaoqiniaoer --url 'https://zaoqiniaoerhannile.com/api/mcp' --transport streamable-http
mcp_servers:
wangjingjing1026uwh-hub-zaoqiniaoer:
url: "https://zaoqiniaoerhannile.com/api/mcp" {
"McpServers": {
"wangjingjing1026uwh-hub-zaoqiniaoer": {
"Transport": "http",
"Url": "https://zaoqiniaoerhannile.com/api/mcp"
}
}
} assistant mcp add wangjingjing1026uwh-hub-zaoqiniaoer -t streamable-http -u 'https://zaoqiniaoerhannile.com/api/mcp'
{
"mcpServers": {
"wangjingjing1026uwh-hub-zaoqiniaoer": {
"type": "http",
"url": "https://zaoqiniaoerhannile.com/api/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
- 27 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 63
First indexed and scored.
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://zaoqiniaoerhannile.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zaoqiniaoerhannile.com | CN=YE1,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5fd4cffb4bf628f7525a43725e9e8f359a0 |
| SANs: www.zaoqiniaoerhannile.com, zaoqiniaoerhannile.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of zaoqiniaoerhannile.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| zaoqiniaoerhannile.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://zaoqiniaoerhannile.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://zaoqiniaoerhannile.com/api/mcp | HTTPS enforced | 301 | https://zaoqiniaoerhannile.com/api/mcp |
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_verification_result 查核实进度和结果 ~57
按下单时拿到的 order_id 查这一单到哪一步了；已经出报告的话，返回三个人各自看到的内容。
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | 下单时返回的 order_id |
No output schema declared.
No examples provided.
verify_place 派真人去现场核实 ~238
派三个互不相识的真人去中国境内的某个实际地点（工厂、门店、公司办公地）实地核实，拍门头照、进店问一句、各自独立写下判断，出一份报告。适合回答"这家供应商是不是真的存在/真的在营业/招牌和地址对不对得上"这类只有到过现场的人才知道的问题。下单会从账户余额扣款。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | 详细地址。地址和网址至少要有一个 |
| budget_yuan | number | – | 预算（人民币元），不填按最低价。给得多，观察员拿得多，接单更快 |
| claim | string | yes | 你想让真人帮你确认的那句话，例如「这个地址真的有一家在营业的工厂」 |
| name | string | yes | 要核实的对象名称，例如「某某精密机械有限公司」 |
| url | string | – | 对方的网店/主页链接。地址和网址至少要有一个 |
No output schema declared.
No examples provided.
What is the io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server?
io.github.wangjingjing1026uwh-hub/zaoqiniaoer is an MCP server listed in the public MCP registry as io.github.wangjingjing1026uwh-hub/zaoqiniaoer. Send three unrelated real people to a physical address in China and get back what they actually saw. This page covers its hosted endpoint (https://zaoqiniaoerhannile.com/api/mcp).
Is the io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server safe to use?
io.github.wangjingjing1026uwh-hub/zaoqiniaoer scores 64 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 io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server expose?
io.github.wangjingjing1026uwh-hub/zaoqiniaoer exposes 2 tools: verify_place, get_verification_result. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Does the io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server require authentication?
No. We connected to io.github.wangjingjing1026uwh-hub/zaoqiniaoer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server still maintained?
io.github.wangjingjing1026uwh-hub/zaoqiniaoer 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.