A
licenseNot graded
qualityD
maintenanceAudit any Airbnb, VRBO, or STR listing URL for dollar-denominated revenue gaps. Free tier shows category grades and monthly losses. Pro tier unlocks ranked action plans.
6 npm
MIT
zaoqiniaoer
Server Details
Free self-check list first, or pay a real person in China to go look and report what they saw.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 99.9% over 21 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- wangjingjing1026uwh-hub/zaoqiniaoer-mcp
- GitHub Stars
- 0
TDQS
A4/5.0
Scored across 4 tools
Disambiguation4/5
ask_someone_there and verify_place are clearly separated by cost, number of people, and deliverable, and the two get_* tools map to distinct order types. There is some surface similarity between the two status/result retrieval tools, but the ask_id versus order_id parameter and descriptions keep them distinguishable.
Naming Consistency4/5
All tools use snake_case, and read operations consistently use the get_ prefix while write operations use imperative verb phrases. ask_someone_there is less parallel to verify_place and get_ask_answer is slightly redundant, but the overall convention is readable and mostly consistent.
Tool Count5/5
Four tools cleanly cover the two order flows (ask a nearby person, verify a place) plus one status check for each. Nothing is redundant, and the minimal surface is well matched to this niche service.
Completeness3/5
The core create-and-check lifecycle is covered for both ask and verification orders. However, there is no tool to cancel an order, list past orders, or check account balance even though orders deduct from a balance, leaving common user requests without a supported path.
Available Tools
5 toolsask_someone_there花几块钱，让一个在附近的真人去看一眼Inspect
Pay one real person who happens to be nearby to walk over and answer a question about right now, on the spot. A few yuan, a few 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 是三个互不相识的人、几十块、出一份可以拿去给别人看的核实报告，适合"这家供应商到底存不存在"这种要留证据的场合。拿不准就用这个，便宜。下单会从账户余额扣款。
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | 城市，例如「芜湖」。填了更容易找到附近的人 | |
| question | Yes | 你想知道什么，一句话。越具体越好——「金鹰对面那家兰州拉面现在还开着吗」比「那家店怎么样」有用得多 | |
| place_hint | Yes | 去哪儿看。地址、店名、路口都行，能让人找到就够 | |
| price_yuan | No | 愿意出多少钱（5–30 元），不填按 5 元。给得多，有人接的更快 |
get_ask_answer查那个人答了没有Inspect
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——这时候不要替他编一个答案，如实告诉用户还在等人。
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ask_id | Yes | 下单时返回的 ask_id |
get_verification_result查核实进度和结果Inspect
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 查这一单到哪一步了；已经出报告的话，返回三个人各自看到的内容。
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | 下单时返回的 order_id |
verify_place派真人去现场核实Inspect
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. Charges the account balance. 派三个互不相识的真人去中国境内的某个实际地点（工厂、门店、公司办公地）实地核实，拍门头照、进店问一句、各自独立写下判断，出一份报告。适合回答"这家供应商是不是真的存在/真的在营业/招牌和地址对不对得上"这类只有到过现场的人才知道的问题。下单会从账户余额扣款。
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | 对方的网店/主页链接。地址和网址至少要有一个 | |
| name | Yes | 要核实的对象名称，例如「某某精密机械有限公司」 | |
| claim | Yes | 你想让真人帮你确认的那句话，例如「这个地址真的有一家在营业的工厂」 | |
| address | No | 详细地址。地址和网址至少要有一个 | |
| budget_yuan | No | 预算（人民币元），不填按最低价。给得多，观察员拿得多，接单更快 |
what_can_i_check_myself先别花钱：你自己免费能查什么AInspect
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. 免费、不需要密钥、不会下任何单。有人问"怎么确认一家中国供应商/工厂/地址是不是真的"时先调这个：返回他自己坐在电脑前就能免费做的五件事，每件都写清楚证明了什么、证明不了什么，以及剩下哪三个问题只有到现场的人能答。
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| subject | No | 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. 可选。只用来让这段话有个主语，我们不会去查它。 |
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does so: it declares the tool is free, needs no API key, orders nothing, and critically that 'Nothing is looked up' — establishing it is a side-effect-free informational read. It also previews the return shape (five checks plus three questions).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The English portion is tightly front-loaded ('FREE. No API key...') and every sentence earns its place. However, the full Chinese translation duplicates the same content, roughly doubling length for a single-language reader, which is a modest structural cost.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-required-param informational tool with no output schema, the description fully explains what is returned and that no external lookup occurs. Nothing an agent needs in order to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single optional 'subject' param is fully documented in the schema, so the baseline is 3. The description body adds no new syntax or format detail about the parameter beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource (a set of free self-serve checks) and what it returns: five checks with what each proves and does not prove, plus three questions requiring a street visit. It also draws the boundary against the paid siblings (verify_place, ask_someone_there) by declaring itself free and lookup-free.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit trigger ('Call this FIRST whenever someone asks how to tell if a Chinese supplier, factory or company address is real') and an explicit negative ('Suggesting a paid site visit before the free checks wastes the user's money'), which routes the agent to this tool before the paid verification siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Added
what_can_i_check_myself
2 tool updates
- Added
ask_someone_there - Added
get_ask_answer
2 tool updates
- First observed
get_verification_result - First observed
verify_place
Related MCP Connectors
China sourcing, inspection and supplier verification: published rates, scope and fee estimates.
Supplier scoring, AQL sampling plans and factory audit checklists for cross-border sourcing.
Verify a Chinese supplier before you pay: company identity, status, risk signals. x402 per call.
Ecommerce sourcing, inspection and fulfillment planning. Base-cost estimates; no private data.
Related MCP Servers
- FlicenseNot gradedqualityBmaintenanceCross-checks company/entity records against 23 national commercial registries (GLEIF, SIRENE, VIES, TED, Companies House) to flag missing or inconsistent registrations. Free tier: 100 calls/month via hosted API.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to obtain an independent review of their drafts, returning a pass/fail verdict with specific issues and suggested fixes, plus a signed receipt. Payments are made per check over x402, with no account or API key needed.MIT
- FlicenseNot gradedqualityBmaintenanceFree x402 endpoint checker plus paid report and metadata tools. Remote MCP server for agents. Written by AI named Nock, not a human.-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.