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.

御府和田玉 在售作品查询

REMOTE · WWW.163YU.COM

Live Hetian jade catalog from Yufu, Shanghai: search, prices, jade Q&A, viewing and order requests.

Available components

+6 this week 73 Trust /100

Last scanned (21 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 Security69
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5152 tokens (~177/item across 29 items; 29 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +3
    • HSTS header: fail → pass ▲ security
  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 15 Nov 26 0
    • Tool “request_viewing” rewrote its description, which is the text the model reads security
    • Schema quality: 4524 → 5152 ▼ functional
    • Destructive annotations: pass → 100 functional
    • Server version: 3.1.0 → 3.2.1 functional
    • New tool “find_series” functional
    • New tool “request_custom” functional
    • New tool “wishlist_add” functional
    • New tool “wishlist_remove” functional
    • “request_viewing” added an optional parameter “purpose” cosmetic
    • “request_viewing” made “product_id” optional cosmetic
  • 13 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “create_order_intent” rewrote its description, which is the text the model reads security
    • Tool “request_viewing” rewrote its description, which is the text the model reads security
    • Schema quality: 3539 → 4524 ▼ functional
    • Tool coverage: 64% → 55% ▼ functional
    • Tool “ask_knowledge” now declares an output schema ▲ functional
    • Tool “compare_products” now declares an output schema ▲ functional
    • Tool “corporate_gift” now declares an output schema ▲ functional
    • Tool “create_order_intent” now declares an output schema ▲ functional
    • Tool “find_bangle” now declares an output schema ▲ functional
    • Tool “get_brand_facts” now declares an output schema ▲ functional
    • Tool “get_order_status” now declares an output schema ▲ functional
    • Tool “get_price_reference” now declares an output schema ▲ functional
    • Tool “get_product” now declares an output schema ▲ functional
    • Tool “gift_advisor” now declares an output schema ▲ functional
    • Tool “handoff_to_human” now declares an output schema ▲ functional
    • Tool “new_arrivals” now declares an output schema ▲ functional
    • Tool “request_viewing” now declares an output schema ▲ functional
    • Tool “same_budget_choices” now declares an output schema ▲ functional
    • Tool “search_products” now declares an output schema ▲ functional
    • Tool “shop_advisor” now declares an output schema ▲ functional
    • Tool “store_viewing_slots” now declares an output schema ▲ functional
    • Tool “subscribe_new_arrivals” now declares an output schema ▲ functional
    • Tool “unsubscribe_new_arrivals” now declares an output schema ▲ functional
    • First check of Tool coverage: 100 functional
    • Server version: 3.0.0 → 3.1.0 functional
    • New tool “find_by_record” functional
    • New tool “get_certificate_info” functional
    • New tool “avoid_pitfalls” functional
    • New tool “craft_guide” functional
    • New tool “get_policies” functional
    • New tool “zodiac_and_festival” functional
    • “create_order_intent” added an optional parameter “confirm_token” cosmetic
    • “request_viewing” added an optional parameter “confirm_token” cosmetic
  • 12 Nov 26 0
    • Tool “request_viewing” rewrote its description, which is the text the model reads security
    • Tool “search_products” rewrote its description, which is the text the model reads security
    • Schema quality: 2132 → 3539 ▼ functional
    • Tool coverage: 69% → 64% ▼ functional
    • Server version: 2.7.0 → 3.0.0 functional
    • New tool “corporate_gift” functional
    • New tool “find_bangle” functional
    • New tool “new_arrivals” functional
    • New tool “same_budget_choices” functional
    • New tool “shop_advisor” functional
    • New tool “store_viewing_slots” functional
    • New tool “subscribe_new_arrivals” functional
    • New tool “unsubscribe_new_arrivals” functional
  • 11 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “ask_knowledge” rewrote its description, which is the text the model reads security
    • Tool “compare_products” rewrote its description, which is the text the model reads security
    • Tool “create_order_intent” rewrote its description, which is the text the model reads security
    • Tool “get_brand_facts” rewrote its description, which is the text the model reads security
    • Tool “get_price_reference” rewrote its description, which is the text the model reads security
    • Tool “get_product” rewrote its description, which is the text the model reads security
    • Tool “request_viewing” rewrote its description, which is the text the model reads security
    • Tool “search_products” rewrote its description, which is the text the model reads security
    • Schema quality: 111 → 193 ▼ functional
    • Tool coverage: 37% → 69% ▲ functional
    • Server version: 2.6.0 → 2.7.0 functional
    • New tool “gift_advisor” functional
    • New tool “handoff_to_human” functional
    • “ask_knowledge” reworded the description of “question” cosmetic
    • “compare_products” reworded the description of “ids” cosmetic
    • “get_price_reference” reworded the description of “group” cosmetic
    • “get_product” reworded the description of “id” cosmetic
    • “request_viewing” reworded the description of “mode” cosmetic
    • “request_viewing” reworded the description of “preferred_time” cosmetic
    • “request_viewing” reworded the description of “product_id” cosmetic
    • “search_products” reworded the description of “award_only” cosmetic
    • “search_products” reworded the description of “max_price” cosmetic
    • “search_products” reworded the description of “min_price” cosmetic
    • “search_products” reworded the description of “query” cosmetic
    • Tool “ask_knowledge” changed its title: 和田玉知识问答 cosmetic
    • Tool “compare_products” changed its title: 对比几件作品 cosmetic
    • Tool “create_order_intent” changed its title: 提交下单意向 cosmetic
    • Tool “get_brand_facts” changed its title: 品牌与门店资料 cosmetic
    • Tool “get_order_status” changed its title: 查订单状态 cosmetic
    • Tool “get_price_reference” changed its title: 价格参考 cosmetic
    • Tool “get_product” changed its title: 查一件作品 cosmetic
    • Tool “request_viewing” changed its title: 预约视频看货/到店看货 cosmetic
    • Tool “search_products” changed its title: 查御府在售作品 cosmetic
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://www.163yu.com/agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=163yu.com CN=YE1,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA384 53c84adba8fb5d2087eee36266c65943fc6
SANs: 163yu.com, m.163yu.com, www.163yu.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 www.163yu.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
163yu.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
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'self' https://*.163yu.com https://*.qianshuiyu.com
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.163yu.com/agent/mcp Verified 200
http (plaintext) http://www.163yu.com/agent/mcp Inconclusive 405
MCP tools · 29 exposed · ~4,903 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_knowledge ~100

回答和田玉知识与御府品牌问题,例如怎么挑、真假与证书、籽料和山料、手镯尺寸、题材寓意、价格行情、门店与退换。从御府官网的指南、问答、题材页检索原文摘录并附链接。English questions supported.

NameTypeReqDescription
limitinteger––
questionstringyes客人的问题原话
NameTypeReqDescription
ai_labelobject––
answersarray––
notestring––
questionstring––
sourcestring––

No examples provided.

avoid_pitfalls ~96

客人担心买到假货、被坑,或问“怎么防俄料冒充”“假皮”“假证书”“羊脂是不是真的”时用:返回常见的坑、自己怎么核对、在御府怎么核对,附官网指南链接。topic 可填关键词(如 证书、皮、籽料、退换)。

NameTypeReqDescription
topicstring––
NameTypeReqDescription
ai_labelobject––
countinteger––
notestring––
pitfallsarray––

No examples provided.

compare_products ~65

对比 2~6 件作品(官网编号),并排返回料子、重量、尺寸、价格、获奖。客人在几件之间犹豫时用。

NameTypeReqDescription
idsarrayyes官网作品编号列表,如 ["99654","96413"]
NameTypeReqDescription
ai_labelobject––
missingarray––
productsarray––

No examples provided.

corporate_gift ~210

企业或团体批量送礼时用(例如"公司年底送 20 位客户每份 3000 左右,2 位重要客户每份 2 万")。按"送谁、几份、每份预算"分档,从官网在售作品里搭配一组(一物一价,每份都是不同作品),给出每档的件数、器型搭配、小计和合计。礼盒、刻字、开票、配送和批量是否有优惠都要顾问确认:把方案交给 handoff_to_human(reason 选"大额或多件")。不要自行承诺折扣。

NameTypeReqDescription
occasionstring–春节/中秋/商务/开业/答谢等
tiersarrayyes分档,例:[{"who":"重要客户","count":2,"budget":20000},{"who":"客户","count":20,"budget":3000}]
NameTypeReqDescription
ai_labelobject––
occasionstring––
planarray––
totalnumber––
total_textstring––

No examples provided.

craft_guide ~81

客人问浮雕、圆雕、镂空、薄意、俏色、阴刻、链雕活环、仿古、素面、抛光是什么、怎么看时用;每种工艺附在售作品举例(有的话)。craft 可填工艺名。

NameTypeReqDescription
craftstring––
NameTypeReqDescription
ai_labelobject––
countinteger––
craftsarray––
notestring––

No examples provided.

create_order_intent ~247

客人明确要买某件有标价的在售作品、并同意把手机号交给御府客服时用(customer_confirmed=true),返回订单号。不在对话中扣款:客服会联系客人核对后发送支付宝/微信付款方式,付款前不锁定作品。客人想讲价就改用 handoff_to_human。(两步确认:首次调用返回 status=needs_confirmation、要向客人复述的内容和 confirm_token;客人明确确认后,用同样参数加 confirm_token 再调用一次才会提交。dry_run 只校验不提交。)

NameTypeReqDescription
citystring–收货城市
confirm_tokenstring–首次调用返回的确认码;客人确认后带上它再调用
customer_confirmedbooleanyes–
dry_runboolean––
namestring––
notestring––
pay_methodstring––
phonestringyes中国大陆 11 位手机号
product_idstringyes–
wechatstring––
NameTypeReqDescription
ai_labelobject––
confirm_tokenstring––
errorstring––
nextstring––
okboolean––
order_idstring––
read_back_to_customerstring––
statusstring––

No examples provided.

find_bangle ~209

客人在挑手镯、说手围或圈口时用:按手围(厘米)或圈口(内径 mm)筛选在售手镯,只给出圈口合适的,并说明怎么量、哪些手镯需要顾问现场量圈口。预算、材质可一起传。手围 16 厘米大约对应内径 55~57 mm。不要凭猜给圈口,问不到就先用 shop_advisor 问。

NameTypeReqDescription
inner_mmnumber–圈口/内径(毫米),如 56;客人说“戴 56 圈”就用这个
limitinteger––
materialstring–可选:白玉/碧玉/籽料等
max_pricenumber––
min_pricenumber––
wrist_cmnumber–手围(厘米),如 16
NameTypeReqDescription
ai_labelobject––
modestring––
recommendationsarray––
statusstring––
total_matchedinteger––

No examples provided.

find_by_record ~177

找在售作品里有获奖记录或拍卖上拍记录的:kind=award(获奖)/auction(上拍)/any;可按赛事(陆子冈杯、玉龙奖、神工奖、百花奖、天工奖、良渚杯)、奖级(金奖/银奖/铜奖/优秀)、年份、预算筛。每件附记录出处。拍卖图录估价不是成交价;不代表现售价格,也不代表升值。同名作品不一定是同一件。

NameTypeReqDescription
conteststring––
kindstring––
levelstring––
limitinteger––
max_pricenumber––
min_pricenumber––
yearstring––
NameTypeReqDescription
ai_labelobject––
in_sale_summaryobject––
kindstring––
notestring––
resultsarray––
totalinteger––

No examples provided.

find_series ~93

客人喜欢某一件(或那件已经卖掉)想看同系列时用:按同题材同料子、同样皮色的籽料、同器型相近价位三组给出在售作品。传 id(官网编号)。同一块料出的作品暂无记录。

NameTypeReqDescription
idstringyes官网作品编号
limitinteger––
NameTypeReqDescription
ai_labelobject––
foundboolean––
groupsarray––
in_saleboolean––
notestring––
totalinteger––

No examples provided.

get_brand_facts ~188

御府和田玉的可核验资料:2002 年创立于上海、创始人付雪飞、门店(上海浦东新区龙东大道3800弄棕榈泉花园,需预约)、获奖记录 200 余项(其中 124 项有证书实拍)、拍卖记录(附出处)、每件附国检证书、门店终身免费保养。客人问"御府靠不靠谱""门店在哪""获过什么奖"时用。topic 填 awards 或 auctions 可拿到明细。注意:御府和田玉 ≠ 付雪飞玉雕(付雪飞是创始人);"上海御府集团"不是御府和田玉;不要提供或编造电话号码。

NameTypeReqDescription
topicstring––
NameTypeReqDescription
ai_labelobject––
brandobject––

No examples provided.

get_certificate_info ~64

国检证书证明什么、不证明什么(产地、籽料山料、白度叫法、价值)、怎么自己查验;带 product_id 时说明这一件的证书要向顾问确认。

NameTypeReqDescription
product_idstring––
NameTypeReqDescription
ai_labelobject––
how_to_verifyarray––
not_provenarray––
what_you_getstring––

No examples provided.

get_order_status ~29

按订单号查询下单意向的状态。

NameTypeReqDescription
order_idstringyes–
NameTypeReqDescription
ai_labelobject––
foundboolean––
order_idstring––
statusstring––

No examples provided.

get_policies ~80

退换(非定制 7 天无理由)、终身免费保养、证书、付款方式(对话中不收款)、发货、定制、到店预约、隐私的结构化说明,附出处;客人问“能退吗”“怎么付款”“有保养吗”时用。

Input schema present but exposes no named parameters.

NameTypeReqDescription
aftercareobject––
ai_labelobject––
notestring––
paymentobject––
returnsobject––

No examples provided.

get_price_reference ~130

御府官网在售作品的价格参考(每月更新):按器型、重量、籽料/山料、颜色、皮色、题材分组的中间价和区间。适合回答"和田玉手镯/玉牌/挂件大概多少钱"。group 可填 手镯、玉牌、青花、观音 等。这是在售标价的统计,不是估价,也不代表升值。

NameTypeReqDescription
groupstring–关键词,例:手镯 / 玉牌 / 观音
NameTypeReqDescription
ai_labelobject––
errorstring––
groupsobject––
how_to_readstring––

No examples provided.

get_product ~87

按官网作品编号(5~6 位数字,如 99654)查详细资料:规格、作品介绍、获奖与上拍出处、常见问题、证书与保养说明、看货和购买方式。客人提到具体编号或想深入了解某一件时用。

NameTypeReqDescription
idstringyes官网作品编号,如 99654
NameTypeReqDescription
ai_labelobject––
dossierobject––
foundboolean––
messagestring––
productobject––

No examples provided.

gift_advisor ~347

按"送给谁、什么场合、预算"从在售作品里挑 3~6 件,给出适合的理由(器型、传统寓意、料子、重量)和一句贺卡文案。什么时候用:客人要送人,例如"给父亲祝寿,2万左右""送领导开业礼""女朋友生日5000以内""宝宝满月"。可以只传 text(客人原话),也可以分别传 who/occasion/预算。如果返回 need_more_info,先问客人缺的那几项,再调用一次。寓意只是传统说法,不要说成有功效,也不要承诺升值。

NameTypeReqDescription
limitinteger––
max_pricenumber–预算上限(人民币元)
min_pricenumber–预算下限(人民币元)
occasionstring–场合:祝寿/生日/春节/中秋/新婚/纪念日/满月/本命年/乔迁/开业/升职/商务/母亲节/父亲节
textstring–客人原话,例:给我爸70大寿,预算2万左右
typestring–可选,指定器型:手镯/挂件/玉牌/手把件/摆件/手串
whostring–送给谁:父亲/母亲/长辈/爱人/女友/男友/孩子/领导/客户/朋友/新人/自己
NameTypeReqDescription
ai_labelobject––
card_textstring––
max_pricenumber|null––
min_pricenumber|null––
need_more_infoarray––
occasionstring––
recommendationsarray––
total_matchedinteger––
whostring––

No examples provided.

handoff_to_human ~338

遇到你不该自己回答的情况,就转给御府的真人顾问:讲价或要折扣、鉴定或真假疑问、投诉或售后、定制、大额或多件、其他你没把握的问题。summary 用一两句话写清:客人想要什么、哪件作品、预算、卡在哪里。客人愿意留手机号或微信时,征得同意后填上并设 customer_confirmed=true,线索会进御府销售系统并通知顾问;客人不愿意留也没关系,会返回顾问的企业微信链接,把它给客人即可。不要自己承诺折扣或回复时间,不要编造任何电话号码。

NameTypeReqDescription
customer_confirmedboolean–留了联系方式时必须为 true(客人已同意交给御府顾问)
dry_runboolean–只校验不提交(测试用)
phonestring–客人同意后留的大陆手机号,可选
product_idstring–相关作品编号,可选
reasonstringyes–
source_aistring–你是哪个 AI 助手,例:豆包/元宝/千问/ChatGPT
summarystringyes一两句话的摘要,例:客人看中99654虎虎生威,预算2万,想问能否优惠,在上海可到店
wechatstring–客人同意后留的微信号,可选
NameTypeReqDescription
ai_labelobject––
errorstring––
messagestring––
okboolean––
reasonstring––
submittedboolean––

No examples provided.

new_arrivals ~74

查御府最近上架的在售作品(默认 7 天)。客人问“最近有什么新货”“有没有刚到的”时用;也可以先拿这个给客人看,再问要不要按条件订阅。

NameTypeReqDescription
daysinteger––
limitinteger––
NameTypeReqDescription
ai_labelobject––
countinteger––
daysinteger––
new_arrivalsarray––

No examples provided.

request_custom ~270

客人想定制(指定题材、刻字、尺寸、送人)时用:把客人说的整理成需求单(题材、用途、器型、料子、预算、尺寸、刻字、时间、参考链接)。没留手机号只返回需求单和顾问企业微信;客人同意留大陆手机号后提交给御府顾问评估报价。不要出 AI 效果图冒充实物,不承诺价格和工期。

NameTypeReqDescription
budgetstring–预算
customer_confirmedboolean––
deadlinestring–希望什么时候要
dry_runboolean––
engravestring–刻字
materialstring–料子偏好
namestring––
notestring–其他要求
phonestring––
referencestring–参考图/链接
sizestring–尺寸/手围
source_aistring––
themestring–题材
typestring–器型
usestring–用途/送谁
wechatstring––
NameTypeReqDescription
ai_labelobject––
confirm_tokenstring––
errorstring––
okboolean––
read_back_to_customerstring––
sheetobject––
statusstring––
submittedboolean––
summarystring––

No examples provided.

request_viewing ~490

客人想先看实物时用:视频看货(mode=video,顾问用企业微信视频展示自然光、上手、称重和证书,适合外地客人),或到上海浦东门店看货(mode=store,上海浦东新区龙东大道3800弄棕榈泉花园,需预约)。必须先征得客人同意并拿到他的中国大陆手机号,再把 customer_confirmed 设为 true。到店看货请先用 store_viewing_slots 拿到可约时段,让客人挑一个,把“日期 时段”填进 preferred_time;视频看货时间更灵活。这不是下单,不锁货、不付款。(两步确认:首次调用返回 status=needs_confirmation、要向客人复述的内容和 confirm_token;客人明确确认后,用同样参数加 confirm_token 再调用一次才会提交。dry_run 只校验不提交。) 也可以预约到店免费保养(purpose=care,御府作品终身免费清洗维护)或参观门店里的荣誉展厅(purpose=gallery)。

NameTypeReqDescription
confirm_tokenstring–首次调用返回的确认码;客人确认后带上它再调用
customer_confirmedbooleanyes客人已同意提交,必须为 true
dry_runboolean–只校验不提交(测试用)
modestring–video=视频看货(默认),store=到店看货
namestring–称呼,可选
notestring–备注,可选,最多 200 字
phonestringyes客人的中国大陆 11 位手机号
preferred_timestring–客人方便的时间,例:今晚8点 / 周六下午
product_idstring–官网作品编号(先用 search_products 或 gift_advisor 确认在售)
purposestring–view=看货(默认,要 product_id);care=到店免费保养(买过的作品,product_id 可填原编号或不填);gallery=参观门店里的荣誉展厅和付雪飞作品(不用 product_id)
NameTypeReqDescription
ai_labelobject––
confirm_tokenstring––
errorstring––
nextstring––
okboolean––
read_back_to_customerstring––
statusstring––
submittedstring––

No examples provided.

same_budget_choices ~184

客人有预算但在几件之间犹豫,或问“同样的钱买什么好”时用:在预算 ±20% 的范围里给出 4 条不同路子(白度高的小件 / 分量足的大件 / 有获奖出处的 / 籽料带皮特色),每条给一件实例、好处和取舍。不评判谁更值钱,帮客人按用途做选择;最后引导预约视频看货一起对比。

NameTypeReqDescription
budgetnumber–预算(元),如 50000
materialstring––
textstring–客人原话,可从里面识别预算
typestring–可选:只在这个器型里比,如 手镯/玉牌/挂件
NameTypeReqDescription
ai_labelobject––
pathsarray––
statusstring––

No examples provided.

search_products ~280

查询上海御府和田玉官网【当前在售】的作品,实时同步,一物一价,返回价格、重量、尺寸、获奖出处和官网链接。什么时候用:客人想买或想看具体作品,例如"20万左右的籽料手镯""10万以内的观音牌""获奖的把件"。query 直接写客人原话,预算会自动识别。需求说得不清楚(没预算、没器型)时先用 shop_advisor 问清楚;如果是送人,优先用 gift_advisor。结果不锁货、不能付款;想看实物用 request_viewing,讲价或疑问用 handoff_to_human。English queries are fine.

NameTypeReqDescription
award_onlyboolean–只看有获奖记录的作品
limitinteger––
max_pricenumber–最高价(人民币元),可不填
min_pricenumber–最低价(人民币元),可不填
querystring–客人的需求原话,例:20万左右的籽料手镯 / 获奖的观音牌 / white jade bangle under $10000
sortstring––
NameTypeReqDescription
ai_labelobject––
filtersobject––
notestring––
querystring––
resultsarray––
totalinteger––

No examples provided.

shop_advisor ~292

客人买和田玉但需求说得不清楚时,优先用这个(例如"想买个手镯""有没有好的玉牌")。它会先返回 need_more_info 和要问客人的 2~3 个问题(预算、器型、手围、送谁),你把问题问完、把客人的回答拼进 text 再调用一次,就会推荐 3 件不同价位的在售作品,并说明区别;手镯会按手围换算建议内径。送人的需求会自动转成送礼推荐。不要在没问清楚时就推荐一堆作品。

NameTypeReqDescription
limitinteger––
materialstring–可选:籽料/白玉/碧玉/青花等
max_pricenumber––
min_pricenumber––
textstringyes客人的需求原话,第二次调用时把客人对问题的回答也拼进来,例:想买个手镯,3到5万,手围16
typestring–可选:手镯/挂件/玉牌/手把件/摆件/手链手串
wrist_cmnumber–可选:手围(厘米),买手镯时用
NameTypeReqDescription
ai_labelobject––
recommendationsarray––
statusstring––

No examples provided.

store_viewing_slots ~103

查上海浦东门店最近两周可以预约的到店时段(日期+时间点)。客人想约到店看货时先用这个,把日期和时段列给客人挑,再用 request_viewing(mode=store,preferred_time 填“日期 时段”)提交。时间和休息日以顾问确认为准。

NameTypeReqDescription
daysinteger–看未来几天,默认 14
NameTypeReqDescription
ai_labelobject––
daysarray––
modestring––
storestring––

No examples provided.

subscribe_new_arrivals ~242

客人想要“有合适的再通知我”时用(御府不降价,所以是到货提醒不是降价提醒):按器型、题材关键词、预算订阅,有匹配的新品上架时通知御府顾问去联系客人。必须先告诉客人会把联系方式交给御府顾问、可随时退订,客人同意后再提交,并把 customer_confirmed 设为 true。不要承诺一定会有货,也不要承诺价格。

NameTypeReqDescription
customer_confirmedbooleanyes–
keywordstring–题材或特征关键词,如 观音/籽料/满皮/山水
max_pricenumber––
min_pricenumber––
phonestring–客人同意后留的大陆手机号
source_aistring–你是哪个 AI 助手
typestring–器型,如 手镯/玉牌/挂件/平安扣
wechatstring–或微信号
NameTypeReqDescription
ai_labelobject––
errorstring––
okboolean––
subscription_idstring––

No examples provided.

unsubscribe_new_arrivals ~37

客人不想再收到新品提醒时用,带上订阅编号 subscription_id。

NameTypeReqDescription
subscription_idstringyes–
NameTypeReqDescription
ai_labelobject––
messagestring––
okboolean––

No examples provided.

wishlist_add ~133

客人看中几件还没决定时用:把在售作品编号加入心愿单;这些作品有人在约看或下单、或者有同类新品上架时,御府顾问会联系客人。需要客人同意留大陆手机号。只想收藏不想留手机号,就给客人官网心愿单页链接。

NameTypeReqDescription
customer_confirmedboolean––
dry_runboolean––
phonestring––
product_idsarrayyes–
source_aistring––
wechatstring––
NameTypeReqDescription
ai_labelobject––
confirm_tokenstring––
countinteger––
errorstring––
okboolean––
read_back_to_customerstring––
statusstring––
wish_idstring––

No examples provided.

wishlist_remove ~34

客人不想再收到心愿单提醒时用,带上 wish_id。

NameTypeReqDescription
wish_idstringyes–
NameTypeReqDescription
ai_labelobject––
messagestring––
okboolean––

No examples provided.

zodiac_and_festival ~223

客人说属相、出生年份、本命年,或者要在某个节日送礼时用:zodiac(如 龙、属羊)或 birth_year(如 1979,会按农历提醒春节前出生的情况)找在售生肖作品并给出本命年时间;festival(春节/元宵/情人节/母亲节/父亲节/七夕/中秋/重阳/元旦/圣诞/本命年)给出下一个日期、送礼思路和在售作品。什么都不传则返回接下来的几个节日。寓意是传统说法,不代表功效。

NameTypeReqDescription
birth_yearinteger––
festivalstring––
limitinteger––
max_pricenumber––
min_pricenumber––
typestring–可选器型:手镯/挂件/玉牌/把件
zodiacstring––
NameTypeReqDescription
ai_labelobject––
festivalobject––
notestring––
nowobject––
resultsarray––
totalinteger––
zodiacobject––

No examples provided.

Install

How do I install the 御府和田玉 在售作品查询 MCP server?

御府和田玉 在售作品查询 is a hosted endpoint at https://www.163yu.com/agent/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 · www.163yu.com

# add to Claude Code
claude mcp add --transport http com-163yu-hetianyu 'https://www.163yu.com/agent/mcp'
Common questions

What is the 御府和田玉 在售作品查询 MCP server?

御府和田玉 在售作品查询 is an MCP server listed in the public MCP registry as com.163yu/hetianyu. Live Hetian jade catalog from Yufu, Shanghai: search, prices, jade Q&A, viewing and order requests. This page covers its hosted endpoint (https://www.163yu.com/agent/mcp).

Is the 御府和田玉 在售作品查询 MCP server safe to use?

御府和田玉 在售作品查询 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 御府和田玉 在售作品查询 MCP server expose?

御府和田玉 在售作品查询 exposes 29 tools: search_products, shop_advisor, corporate_gift, gift_advisor, get_product, and 24 more. Their descriptions and schemas cost roughly 4,903 tokens of context every time the server is loaded.

Does the 御府和田玉 在售作品查询 MCP server require authentication?

No. We connected to 御府和田玉 在售作品查询 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 御府和田玉 在售作品查询 MCP server still maintained?

御府和田玉 在售作品查询 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 御府和田玉 在售作品查询 MCP server?

VerifyMCP ran 12 checks on 御府和田玉 在售作品查询, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about 御府和田玉 在售作品查询: HTTPS. 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.