_ registry / mcp streamable-http · checked 1h ago

zaoqiniaoer-verify

https://zaoqiniaoerhannile.com

Registry code: 3bcdcc5e0bdd505f

api record

你被问到物理世界"此刻"的事情时,通常只有两条路:瞎编,或者说"我无法确认"。这个服务是第三条路——**花几块钱,让一个正好在附近的真人走过去看一眼,把他看到的东西告诉你**。中国境内。

什么时候用:「那家店现在开着吗」「这个充电桩能不能用」「那条路堵不堵」「货架上还有没有货」——这类网上查不到、只有此刻站在那儿的人才知道的事。

endpoint
https://zaoqiniaoerhannile.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is zaoqiniaoer-verify live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is zaoqiniaoer-verify free to use?
Yes — the hub reached it with no key and no payment.
What tools does zaoqiniaoer-verify have?
5 tools: verify_place, get_verification_result, get_ask_answer, ask_someone_there, what_can_i_check_myself.
Is zaoqiniaoer-verify safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99%· all time 99%

latency
1,169ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 290 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • verify a chinese supplier exists on site
  • check status of a site verification order
takes → gives
text, payments → data, images
tools
1 reads1 moves money
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • what_can_i_check_myself open 23h ago

    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. 免费、不需要密钥、不会下任何单。有人问"怎么确认一家中国供应商/工厂/地址是不是真的"时**先调这个**:返回他自己坐在电脑前就能免费做的五件事,每件都写清楚证明了什么、**证明不了什么**,以及剩下哪三个问题只有到现场的人能答。

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "subject": {
          "type": "string",
          "description": "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. 可选。只用来让这段话有个主语,我们不会去查它。"
        }
      }
    }
    arguments 10 lines
  • verify_place moves money unknown never probed

    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. 派三个互不相识的真人去中国境内的某个实际地点(工厂、门店、公司办公地)实地核实,拍门头照、进店问一句、各自独立写下判断,出一份报告。适合回答"这家供应商是不是真的存在/真的在营业/招牌和地址对不对得上"这类只有到过现场的人才知道的问题。下单会从账户余额扣款。

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "claim"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "对方的网店/主页链接。地址和网址至少要有一个"
        },
        "name": {
          "type": "string",
          "description": "要核实的对象名称,例如「某某精密机械有限公司」"
        },
        "claim": {
          "type": "string",
          "description": "你想让真人帮你确认的那句话,例如「这个地址真的有一家在营业的工厂」"
        },
        "address": {
          "type": "string",
          "description": "详细地址。地址和网址至少要有一个"
        },
        "budget_yuan": {
          "type": "number",
          "description": "预算(人民币元),不填按最低价。给得多,观察员拿得多,接单更快"
        }
      }
    }
    arguments 29 lines
  • get_verification_result reads unknown 23h ago

    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 查这一单到哪一步了;已经出报告的话,返回三个人各自看到的内容。

    mcp-tool

    {
      "type": "object",
      "required": [
        "order_id"
      ],
      "properties": {
        "order_id": {
          "type": "string",
          "description": "下单时返回的 order_id"
        }
      }
    }
    arguments 12 lines
  • get_ask_answer unknown 23h ago

    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——这时候不要替他编一个答案**,如实告诉用户还在等人。

    mcp-tool

    {
      "type": "object",
      "required": [
        "ask_id"
      ],
      "properties": {
        "ask_id": {
          "type": "string",
          "description": "下单时返回的 ask_id"
        }
      }
    }
    arguments 12 lines
  • ask_someone_there unknown never probed

    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 是三个互不相识的人、几十块、出一份可以拿去给别人看的核实报告,适合"这家供应商到底存不存在"这种要留证据的场合。拿不准就用这个,便宜。下单会从账户余额扣款。

    mcp-tool

    {
      "type": "object",
      "required": [
        "question",
        "place_hint"
      ],
      "properties": {
        "city": {
          "type": "string",
          "description": "城市,例如「芜湖」。填了更容易找到附近的人"
        },
        "question": {
          "type": "string",
          "description": "你想知道什么,一句话。越具体越好——「金鹰对面那家兰州拉面现在还开着吗」比「那家店怎么样」有用得多"
        },
        "place_hint": {
          "type": "string",
          "description": "去哪儿看。地址、店名、路口都行,能让人找到就够"
        },
        "price_yuan": {
          "type": "number",
          "description": "愿意出多少钱(5–30 元),不填按 5 元。给得多,有人接的更快"
        }
      }
    }
    arguments 25 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3bcdcc5e0bdd505f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3bcdcc5e0bdd505f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3bcdcc5e0bdd505f/badge.svg)](https://brick.blue/agent/3bcdcc5e0bdd505f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.