Skip to content

人生增值(zengzhi.life)MCP server

life.zengzhi/zengzhizengzhi.lifestreamable-httpv1.0.0Scanned

人生增值 ZengZhi — 个人数字资产审计/撮合平台 (digital-asset audit/matchmaking): 公开 tools 免 Key, 个人数据需 Bearer zzk_.

10 tools: 9 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 9 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

9 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the 人生增值(zengzhi.life)MCP server can do

The 人生增值(zengzhi.life)MCP server is published by zengzhi.life, a domain the MCP Registry verified. It has 10 tools. It can create or change data (9 tools: zengzhi_meta, zengzhi_code_of_conduct, zengzhi_directory, zengzhi_public_page and 5 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 9Claude Code: ask
  • zengzhi_account_overview主人账号总览(key 即持有人本人):订单/页面/委托/意向等全貌摘要。需 API Key。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    主人账号总览(key 即持有人本人):订单/页面/委托/意向等全貌摘要。需 API Key。
  • zengzhi_code_of_conduct人生增值平台行为规范(markdown 原文):接入前必读,写明 Agent 的边界与义务。免 key。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    人生增值平台行为规范(markdown 原文):接入前必读,写明 Agent 的边界与义务。免 key。
  • zengzhi_directory公开资产展示页目录(游客可看,笔名出镜、素材保密)。免 key。 Args: cat: 资产类别过滤(T1 经验诀窍 / T2 模板清单 / T3 数据语料 / T4 软件工具 / T5 内容作品 / T6 视觉设计 / T7 垂直影响 / T8 AI 资产);留空=全部 page: 页码,从 1 起 size: 每页条数,默认 24,最大 100No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    公开资产展示页目录(游客可看,笔名出镜、素材保密)。免 key。 Args: cat: 资产类别过滤(T1 经验诀窍 / T2 模板清单 / T3 数据语料 / T4 软件工具 / T5 内容作品 / T6 视觉设计 / T7 垂直影响 / T8 AI 资产);留空=全部 page: 页码,从 1 起 size: 每页条数,默认 24,最大 100
  • zengzhi_meta人生增值平台元信息(端点矩阵唯一事实源):业务结构、八类资产、认证方式、 route_flags 全量端点清单(哪些 key 可调、哪些 HUMAN_ONLY)、每日配额口径、反馈入口。 接入后建议第一条调用。免 key。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    人生增值平台元信息(端点矩阵唯一事实源):业务结构、八类资产、认证方式、 route_flags 全量端点清单(哪些 key 可调、哪些 HUMAN_ONLY)、每日配额口径、反馈入口。 接入后建议第一条调用。免 key。
  • zengzhi_my_market主人的市面四合一快照:deals/mine(成交申报)、deeds/mine(委托书)、 intents/mine(我方购买意向)、intents/received(收到的购买意向),各自原样 JSON。需 API Key。 只读快照;撤回意向、申报成交等写操作走 REST(intents/{id}/cancel、deals/declare),由主人拍板。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    主人的市面四合一快照:deals/mine(成交申报)、deeds/mine(委托书)、 intents/mine(我方购买意向)、intents/received(收到的购买意向),各自原样 JSON。需 API Key。 只读快照;撤回意向、申报成交等写操作走 REST(intents/{id}/cancel、deals/declare),由主人拍板。
  • zengzhi_price_refs价格参考库:同类资产的真实成交/挂牌区间汇总(含来源与时间;非平台估价,平台不作价值鉴定)。需 API Key。 Args: cat: 类别(T1–T8 或其名称);want_range=true 时必填,返回该类别的合计区间 kw: 标题关键词过滤(仅列表模式) page/size: 分页(仅列表模式) want_range: true=改查该 cat 的…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    价格参考库:同类资产的真实成交/挂牌区间汇总(含来源与时间;非平台估价,平台不作价值鉴定)。需 API Key。 Args: cat: 类别(T1–T8 或其名称);want_range=true 时必填,返回该类别的合计区间 kw: 标题关键词过滤(仅列表模式) page/size: 分页(仅列表模式) want_range: true=改查该 cat 的价格区间汇总(/price-refs/range)
  • zengzhi_public_page按 page_id 取单个公开展示页(笔名、简介、SKU 概览;不含私密素材)。免 key。 page_id 来自 zengzhi_directory 返回的条目。原文:https://zengzhi.life/directory/{page_id}No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    按 page_id 取单个公开展示页(笔名、简介、SKU 概览;不含私密素材)。免 key。 page_id 来自 zengzhi_directory 返回的条目。原文:https://zengzhi.life/directory/{page_id}
  • zengzhi_report_detail盘点订单或展示页详情,二选一传参。需 API Key。 Args: order_id: 盘点订单 id(来自 zengzhi_report_orders); include_step0=true 时附带返回该单的 Step0 素材引导问答 page_id: 展示页 id(二选一,传了 page_id 就忽略 order_id)No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    盘点订单或展示页详情,二选一传参。需 API Key。 Args: order_id: 盘点订单 id(来自 zengzhi_report_orders); include_step0=true 时附带返回该单的 Step0 素材引导问答 page_id: 展示页 id(二选一,传了 page_id 就忽略 order_id)
  • zengzhi_report_orders列出主人的深度盘点订单(最近 50 条:单号、类别、状态、关联展示页、自报价)。需 API Key。No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    列出主人的深度盘点订单(最近 50 条:单号、类别、状态、关联展示页、自报价)。需 API Key。
Only reads 1Show 1 read-only tool
  • zengzhi_ping身份自检 + 当日配额快照:确认 key 有效、是谁的 key,回各配额 limit/used/remaining。需 API Key。 被限流/超额时先调它自查,别盲目重试。No findings

    Why it is in this group

    • The name "zengzhi_ping" says "ping": a word for reading.
    Description, as the server wrote it
    身份自检 + 当日配额快照:确认 key 有效、是谁的 key,回各配额 limit/used/remaining。需 API Key。 被限流/超额时先调它自查,别盲目重试。

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:15 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: zengzhi.life does not resolve.

Posture changes

  1. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 9 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http zengzhi https://zengzhi.life/mcp
claude mcp add --transport http zengzhi https://zengzhi.life/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__zengzhi__zengzhi_ping"
    ],
    "ask": [
      "mcp__zengzhi__zengzhi_meta",
      "mcp__zengzhi__zengzhi_code_of_conduct",
      "mcp__zengzhi__zengzhi_directory",
      "mcp__zengzhi__zengzhi_public_page",
      "mcp__zengzhi__zengzhi_account_overview",
      "mcp__zengzhi__zengzhi_report_orders",
      "mcp__zengzhi__zengzhi_report_detail",
      "mcp__zengzhi__zengzhi_price_refs",
      "mcp__zengzhi__zengzhi_my_market"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zengzhi. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/life.zengzhi/zengzhi/verify?hash=27b434e57d6af1c8c8ca4a1306b66cdbedff15db9cee6318d3ac9586755b9b00" | jq -e '.changed == false'

Pinned hash 27b434e57d6a, from Oct 21, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/life.zengzhi/zengzhi/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for life.zengzhi/zengzhi
[![Anlyon Radar](https://radar.anlyon.com/badge/life.zengzhi/zengzhi.svg)](https://radar.anlyon.com/servers/life.zengzhi/zengzhi)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

人生增值(zengzhi.life)MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the 人生增值(zengzhi.life)MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the 人生增值(zengzhi.life)MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the 人生增值(zengzhi.life)MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the 人生增值(zengzhi.life)MCP server have?

10 tools: 9 write, 1 read. zengzhi_meta, zengzhi_code_of_conduct, zengzhi_directory, zengzhi_public_page, zengzhi_account_overview, zengzhi_report_orders, zengzhi_report_detail, zengzhi_price_refs and 2 more.

Does the 人生增值(zengzhi.life)MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the 人生增值(zengzhi.life)MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the 人生增值(zengzhi.life)MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.