人生增值（zengzhi.life）MCP
REMOTE · ZENGZHI.LIFE
人生增值 ZengZhi — 个人数字资产审计/撮合平台 (digital-asset audit/matchmaking): 公开 tools 免 Key, 个人数据需 Bearer zzk_.
Available components
Last scanned (5 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 18 Oct 2026.
Category E-commerce
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1019 tokens (~101/item across 10 items; 10 tools + 0 resources), lean.Pass
- 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 Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 17 Oct 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.
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 +11
- Transport: fail → pass ▲ security
- 10 Oct 26 −9
- Transport: pass → fail ▼ security
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 18 Oct 2026 · Probed https://zengzhi.life/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zengzhi.life | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6891c04ef0410674bce0b3c66b117acfbc4 |
| SANs: www.zengzhi.life, zengzhi.life | ||||||
| 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 zengzhi.life. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| life. | present | 11164 | 8 | Verified |
| zengzhi.life. | absent | 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 | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; connect-src 'self'; img-src 'self' data:; object-src 'none'; base-uri 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zengzhi.life/mcp | Verified | 200 | |
| http (plaintext) | http://zengzhi.life/mcp | Inconclusive | 406 |
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 →
zengzhi_account_overview ~42
主人账号总览（key 即持有人本人）：订单/页面/委托/意向等全貌摘要。需 API Key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zengzhi_code_of_conduct ~44
人生增值平台行为规范（markdown 原文）：接入前必读，写明 Agent 的边界与义务。免 key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zengzhi_directory ~148
公开资产展示页目录（游客可看，笔名出镜、素材保密）。免 key。 Args: cat: 资产类别过滤（T1 经验诀窍 / T2 模板清单 / T3 数据语料 / T4 软件工具 / T5 内容作品 / T6 视觉设计 / T7 垂直影响 / T8 AI 资产）；留空=全部 page: 页码，从 1 起 size: 每页条数，默认 24，最大 100
| Name | Type | Req | Description |
|---|---|---|---|
| cat | string | – | – |
| page | integer | – | – |
| size | integer | – | – |
No output schema declared.
No examples provided.
zengzhi_meta ~77
人生增值平台元信息（端点矩阵唯一事实源）：业务结构、八类资产、认证方式、 route_flags 全量端点清单（哪些 key 可调、哪些 HUMAN_ONLY）、每日配额口径、反馈入口。 接入后建议第一条调用。免 key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zengzhi_my_market ~111
主人的市面四合一快照：deals/mine（成交申报）、deeds/mine（委托书）、 intents/mine（我方购买意向）、intents/received（收到的购买意向），各自原样 JSON。需 API Key。 只读快照；撤回意向、申报成交等写操作走 REST（intents/{id}/cancel、deals/declare），由主人拍板。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zengzhi_ping ~67
身份自检 + 当日配额快照：确认 key 有效、是谁的 key，回各配额 limit/used/remaining。需 API Key。 被限流/超额时先调它自查，别盲目重试。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zengzhi_price_refs ~170
价格参考库：同类资产的真实成交/挂牌区间汇总（含来源与时间；非平台估价，平台不作价值鉴定）。需 API Key。 Args: cat: 类别（T1–T8 或其名称）；want_range=true 时必填，返回该类别的合计区间 kw: 标题关键词过滤（仅列表模式） page/size: 分页（仅列表模式） want_range: true=改查该 cat 的价格区间汇总（/price-refs/range）
| Name | Type | Req | Description |
|---|---|---|---|
| cat | string | – | – |
| kw | string | – | – |
| page | integer | – | – |
| size | integer | – | – |
| want_range | boolean | – | – |
No output schema declared.
No examples provided.
zengzhi_public_page ~79
按 page_id 取单个公开展示页（笔名、简介、SKU 概览；不含私密素材）。免 key。 page_id 来自 zengzhi_directory 返回的条目。原文：https://zengzhi.life/directory/{page_id}
| Name | Type | Req | Description |
|---|---|---|---|
| page_id | integer | yes | – |
No output schema declared.
No examples provided.
zengzhi_report_detail ~122
盘点订单或展示页详情，二选一传参。需 API Key。 Args: order_id: 盘点订单 id（来自 zengzhi_report_orders）； include_step0=true 时附带返回该单的 Step0 素材引导问答 page_id: 展示页 id（二选一，传了 page_id 就忽略 order_id）
| Name | Type | Req | Description |
|---|---|---|---|
| include_step0 | boolean | – | – |
| order_id | integer | – | – |
| page_id | integer | – | – |
No output schema declared.
No examples provided.
zengzhi_report_orders ~44
列出主人的深度盘点订单（最近 50 条：单号、类别、状态、关联展示页、自报价）。需 API Key。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the 人生增值（zengzhi.life）MCP server?
人生增值（zengzhi.life）MCP is a hosted endpoint at https://zengzhi.life/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 · zengzhi.life
claude mcp add --transport http life-zengzhi-zengzhi 'https://zengzhi.life/mcp'
What is the 人生增值（zengzhi.life）MCP server?
人生增值（zengzhi.life）MCP is listed in the public MCP registry as life.zengzhi/zengzhi. 人生增值 ZengZhi, 个人数字资产审计/撮合平台 (digital-asset audit/matchmaking): 公开 tools 免 Key, 个人数据需 Bearer zzk_. This page covers its hosted endpoint (https://zengzhi.life/mcp).
Is the 人生增值（zengzhi.life）MCP server safe to use?
人生增值（zengzhi.life）MCP scores 67 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 人生增值（zengzhi.life）MCP server expose?
人生增值（zengzhi.life）MCP exposes 10 tools: zengzhi_meta, zengzhi_code_of_conduct, zengzhi_directory, zengzhi_public_page, zengzhi_ping, and 5 more. Their descriptions and schemas cost roughly 904 tokens of context every time the server is loaded.
Does the 人生增值（zengzhi.life）MCP server require authentication?
No. We connected to 人生增值（zengzhi.life）MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 人生增值（zengzhi.life）MCP server still maintained?
人生增值（zengzhi.life）MCP is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.