Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Hetianyu is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Live Hetian jade catalog from Yufu, Shanghai: search, prices, jade Q&A, viewing and order requests.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hetianyu-mcp https://www.163yu.com/agent/mcp
# 2 — ask your agent for something these tools do
# search_products, get_product, compare_products and 3 more
Hetianyu costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http hetianyu-mcp https://www.163yu.com/agent/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
查询御府和田玉官网当前在售的和田玉玉雕作品(实时数据,一物一价,带官网链接、价格、重量、获奖出处)。可用自然语言,如“20万左右的籽料手镯”“获奖的观音牌”。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 自然语言需求或关键词 |
| min_price | number | no | — |
| max_price | number | no | — |
| award_only | boolean | no | — |
| sort | string | no | — |
| limit | integer | no | — |
按官网商品编号查询一件作品的详细资料和购买方式。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
对比最多 6 件作品(官网编号)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | — |
御府和田玉品牌、门店、创作者付雪飞的可核验资料(获奖、拍卖记录附出处)。topic 可选 awards / auctions。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | — |
御府和田玉在售作品价格参考(每月更新):按器型、重量、籽料/山料、颜色、皮色、题材分组的中间价和区间。适合回答“和田玉手镯/玉牌/挂件大概多少钱”。group 可填关键词如 手镯、玉牌、青花、观音。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | — |
替客人向御府客服提交“预约视频看货”或“预约到店看货”(上海浦东门店)。只有在客人明确同意、并愿意把手机号交给御府客服时才调用,并把 customer_confirmed 设为 true。这不是下单,不锁货、不付款;客服会打电话或加微信确认时间。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | 官网商品编号(先用 search_products 确认在售) |
| phone | string | yes | 客人的中国大陆 11 位手机号 |
| mode | string | no | video=视频看货,store=到店看货 |
| preferred_time | string | no | 客人希望的时间,如 周六下午 |
| name | string | no | 称呼,可选 |
| note | string | no | 备注,可选,最多 200 字 |
| customer_confirmed | boolean | yes | 客人已同意提交,必须为 true |
| dry_run | boolean | no | 只校验不提交(测试用) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hetianyu or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_products | no tags | |
| get_product | no tags | |
| compare_products | no tags | |
| get_brand_facts | no tags | |
| get_price_reference | no tags | |
| request_viewing | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.4.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Hetianyu can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.