Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.wangjingjing1026uwh-hub/zaoqiniaoer

REMOTE · ZAOQINIAOERHANNILE.COM

Free self-check list first, or pay a real person in China to go look and report what they saw.

0 this week 73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1978 tokens (~395/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ask_someone_there" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 15 Nov 26 0
    • Tool “ask_someone_there” rewrote its description, which is the text the model reads security
    • Tool “verify_place” rewrote its description, which is the text the model reads security
    • Schema quality: 354 → 395 ▼ functional
    • “ask_someone_there” reworded the description of “price_yuan” cosmetic
    • “verify_place” reworded the description of “budget_yuan” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 0
    • Stability: pass → 0.97 functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

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

  • 12 Oct 26 0
    • Tool “ask_someone_there” rewrote its description, which is the text the model reads security
    • Tool “get_ask_answer” rewrote its description, which is the text the model reads security
    • Tool “get_verification_result” rewrote its description, which is the text the model reads security
    • Tool “verify_place” rewrote its description, which is the text the model reads security
    • Schema quality: 307 → 354 ▼ functional
    • Destructive annotations: pass → 0 functional
    • New tool “what_can_i_check_myself” functional
Diagnostics

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 21 Nov 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=YE2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 583ecb227feca01e2b82c5fe43f43fc4431
SANs: www.zaoqiniaoerhannile.com, zaoqiniaoerhannile.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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. DS published 19718 13 Verified
zaoqiniaoerhannile.com. No DS 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
MCP tools · 5 exposed · ~1,428 tokens

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 →

Tool Tokens
ask_someone_there ~456

Pay one real person who happens to be nearby to walk over and answer a question about **right now, on the spot**. PRICE: CNY 5-30 (about US$0.70-4), usually answered within hours. Good for: is this shop open right now, does this charger work, how busy is that street today, is the item still on the shelf — things you cannot search for, that only someone standing there this minute knows. Cheaper and faster than verify_place, but one person and no report. 让一个正好在附近的真人去看一眼,回答一个**当下、现场**的问题,几块钱、几小时内。适合:这家店现在开着吗、这个充电桩能不能用、这条街今天什么样、货架上还有没有货——这类你搜不到、只有此刻站在那儿的人才知道的事。 跟 verify_place 的区别:这个是**一个人、便宜、快**,给的是一句现场描述;verify_place 是三个互不相识的人、几十块、出一份可以拿去给别人看的核实报告,适合"这家供应商到底存不存在"这种要留证据的场合。拿不准就用这个,便宜。下单会从账户余额扣款。

NameTypeReqDescription
citystring–城市,例如「芜湖」。填了更容易找到附近的人
place_hintstringyes去哪儿看。地址、店名、路口都行,能让人找到就够
price_yuannumber–How much to pay, in CNY, 5-30 (about US$0.70-4); defaults to 5. 愿意出多少钱(5–30 元),不填按 5 元。给得多,有人接的更快
questionstringyes你想知道什么,一句话。越具体越好——「金鹰对面那家兰州拉面现在还开着吗」比「那家店怎么样」有用得多

No output schema declared.

No examples provided.

get_ask_answer ~122

Check the status of one ask by ask_id. **Until someone has actually gone and answered, `answer` is null — do not invent an answer in its place.** Tell the user it is still waiting for a person. The entire point of this service is that nothing is made up. 按 ask_id 查一单到哪一步了。**没人答之前 answer 是 null——这时候不要替他编一个答案**,如实告诉用户还在等人。

NameTypeReqDescription
ask_idstringyes下单时返回的 ask_id

No output schema declared.

No examples provided.

get_verification_result ~101

Check progress of one verification by the order_id you got when ordering. Once the report is ready, returns what each of the three people saw, separately — not a merged verdict. We do not tell you what to conclude. 按下单时拿到的 order_id 查这一单到哪一步了;已经出报告的话,返回三个人各自看到的内容。

NameTypeReqDescription
order_idstringyes下单时返回的 order_id

No output schema declared.

No examples provided.

verify_place ~503

Send three strangers — people who have never met — to a physical address in China (factory, shop, or office) on different days, unannounced. Each photographs the storefront, asks one question inside, and writes down what they saw in their own words. You get all three accounts in one report. Use this when the question is "does this supplier actually exist / is it actually operating / does the sign match the address" — things only someone standing there can answer. PRICE: from CNY 700 (about US$99) per address — that is the minimum, and it covers all three people. For comparison, a registry-lookup report with nobody on the ground costs US$50-99, and a full factory audit US$500-1,200. Charged to your account balance; top up at https://zaoqiniaoerhannile.com/developers 派三个互不相识的真人去中国境内的某个实际地点(工厂、门店、公司办公地)实地核实,拍门头照、进店问一句、各自独立写下判断,出一份报告。适合回答"这家供应商是不是真的存在/真的在营业/招牌和地址对不对得上"这类只有到过现场的人才知道的问题。价格:每个地址 ¥700 起(约 $99),这是最低价,三个人的钱都含在里面。下单从账户余额扣款,充值在 https://zaoqiniaoerhannile.com/developers

NameTypeReqDescription
addressstring–详细地址。地址和网址至少要有一个
budget_yuannumber–Budget in CNY. Minimum 700 (about US$99); leave empty to use it. Paying more means each of the three people earns more, and they go sooner. 预算(人民币元),最低 700(约 $99),不填按最低价。给得多,观察员拿得多,接单更快
claimstringyes你想让真人帮你确认的那句话,例如「这个地址真的有一家在营业的工厂」
namestringyes要核实的对象名称,例如「某某精密机械有限公司」
urlstring–对方的网店/主页链接。地址和网址至少要有一个

No output schema declared.

No examples provided.

what_can_i_check_myself ~246

FREE. No API key, no balance, nothing is ordered. Call this FIRST whenever someone asks how to tell if a Chinese supplier, factory or company address is real. Returns the five checks they can do themselves from a desk for nothing — and, for each one, what it proves and **what it does not prove** — plus the three questions that only someone standing on that street can answer. Suggesting a paid site visit before the free checks wastes the user's money. 免费、不需要密钥、不会下任何单。有人问"怎么确认一家中国供应商/工厂/地址是不是真的"时**先调这个**:返回他自己坐在电脑前就能免费做的五件事,每件都写清楚证明了什么、**证明不了什么**,以及剩下哪三个问题只有到现场的人能答。

NameTypeReqDescription
subjectstring–Optional. The company name or address being checked, used only to address the answer to it. **Nothing is looked up** — that is why this tool is free. 可选。只用来让这段话有个主语,我们不会去查它。

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http wangjingjing1026uwh-hub-zaoqiniaoer 'https://zaoqiniaoerhannile.com/api/mcp'
Common questions

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. Free self-check list first, or pay a real person in China to go look and report what they 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 73 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 5 tools: what_can_i_check_myself, verify_place, ask_someone_there, get_ask_answer, get_verification_result. Their descriptions and schemas cost roughly 1,428 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.wangjingjing1026uwh-hub/zaoqiniaoer MCP server?

VerifyMCP ran 12 checks on io.github.wangjingjing1026uwh-hub/zaoqiniaoer, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.wangjingjing1026uwh-hub/zaoqiniaoer: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.