Zhenghe — 正和支付路由与资本保全金库
REMOTE · MCP.ZHENG-HE.TOP · SCANNED SEP 24
Base 主网去中心化支付路由+金库：查 NAV、构造路由支付 calldata、金库存取、绑定引路人分账。存款安全·引路人激励·消费即升值，全部链上可核验。
Available components
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 Security63
- 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 4 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 587 tokens (~146/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Zhenghe — 正和支付路由与资本保全金库 MCP server?
Zhenghe — 正和支付路由与资本保全金库 is a hosted endpoint at https://mcp.zheng-he.top/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 · mcp.zheng-he.top
claude mcp add --transport http top-zheng-he-zhenghe-mcp 'https://mcp.zheng-he.top/mcp'
{
"mcpServers": {
"top-zheng-he-zhenghe-mcp": {
"url": "https://mcp.zheng-he.top/mcp"
}
}
} {
"servers": {
"top-zheng-he-zhenghe-mcp": {
"type": "http",
"url": "https://mcp.zheng-he.top/mcp"
}
}
} [mcp_servers.top-zheng-he-zhenghe-mcp] url = "https://mcp.zheng-he.top/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"top-zheng-he-zhenghe-mcp": {
"type": "remote",
"url": "https://mcp.zheng-he.top/mcp",
"enabled": true
}
}
} openclaw mcp add top-zheng-he-zhenghe-mcp --url 'https://mcp.zheng-he.top/mcp' --transport streamable-http
mcp_servers:
top-zheng-he-zhenghe-mcp:
url: "https://mcp.zheng-he.top/mcp" {
"McpServers": {
"top-zheng-he-zhenghe-mcp": {
"Transport": "http",
"Url": "https://mcp.zheng-he.top/mcp"
}
}
} assistant mcp add top-zheng-he-zhenghe-mcp -t streamable-http -u 'https://mcp.zheng-he.top/mcp'
{
"mcpServers": {
"top-zheng-he-zhenghe-mcp": {
"type": "http",
"url": "https://mcp.zheng-he.top/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Aug 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
First indexed and scored.
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 24 Sept 2026 · Probed https://mcp.zheng-he.top/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.zheng-he.top | CN=YR2,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 2048 | SHA256-RSA | 57a6b291762fb07147f8f4b93eb287be0c6 |
| SANs: mcp.zheng-he.top | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zheng-he.top. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| top. | present | 26780, 41508 | 8, 13 | Verified |
| zheng-he.top. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zheng-he.top/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.zheng-he.top/mcp | HTTPS enforced | 308 | https://mcp.zheng-he.top/mcp |
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 →
affiliate_bind ~138
绑定引路人（一次性、永久、链上不可改）。返回 bindReferrer calldata，签名上链即完成绑定。此后该地址每笔路由消费的 6bps USDC 立即分给引路人，商户捐赠 LOVE 的 20% 同样分账，原子结算。任何 Agent 都可以成为引路人推广正和并永久获取分成。
| Name | Type | Req | Description |
|---|---|---|---|
| binder | string | – | 被绑定地址 0x…（calldata 的 from，仅用于展示） |
| leader | string | yes | 引路人地址 0x…（必填） |
No output schema declared.
No examples provided.
nav_query ~84
查询正和金库实时状态：NAV（净值）、金库 USDC 总资产、LOVE 总份额、累计溢价。只读，无需任何授权。传入 address 可同时查该地址的 LOVE/USDC 余额与浮盈。
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | （可选）要查余额的钱包地址 0x… |
No output schema declared.
No examples provided.
vault_action ~140
正和金库操作。action=deposit：USDC→LOVE（返回 approve+deposit calldata）；action=withdraw：LOVE→USDC（返回 redeem calldata）；action=balance：查 LOVE 余额+NAV+浮盈（只读）。金库无 owner、无管理函数，NAV 单调增长——存款安全由合约字节码保证，可自验。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| address | string | yes | 操作地址 0x…（deposit/withdraw 的接收方，balance 的查询方） |
| amount | number | – | deposit=USDC 数量；withdraw=LOVE 数量 |
No output schema declared.
No examples provided.
zhenghe_route ~225
构造一笔正和路由支付（消费入口）。返回签名就绪的 approve+pay calldata，调用方本地签名上链即完成原子正和支付：商户收 USDC + 捐赠注入金库 + 引路人分账 + NAV 抬升。路由决策：USDC 够→直接付；USDC 不足但 LOVE×NAV 够→赎回 LOVE 付；都不够→返回缺口。私钥永不经过服务器。
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | 支付金额（USDC，必填） |
| leader | string | – | 引路人地址（可选，未绑定时可自引自收） |
| merchant | string | yes | 收款商户地址 0x…（必填） |
| payer | string | – | 付款方地址（可选，传入则按真实余额做路由决策） |
| ref | string | – | 订单引用（可选，将 keccak 为 bytes32） |
No output schema declared.
No examples provided.
What is the Zhenghe — 正和支付路由与资本保全金库 MCP server?
Zhenghe — 正和支付路由与资本保全金库 is an MCP server listed in the public MCP registry as top.zheng-he/zhenghe-mcp. Base 主网去中心化支付路由+金库：查 NAV、构造路由支付 calldata、金库存取、绑定引路人分账。存款安全·引路人激励·消费即升值，全部链上可核验。 This page covers its hosted endpoint (https://mcp.zheng-he.top/mcp).
Is the Zhenghe — 正和支付路由与资本保全金库 MCP server safe to use?
Zhenghe — 正和支付路由与资本保全金库 scores 80 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 Zhenghe — 正和支付路由与资本保全金库 MCP server expose?
Zhenghe — 正和支付路由与资本保全金库 exposes 4 tools: nav_query, zhenghe_route, vault_action, affiliate_bind. Their descriptions and schemas cost roughly 587 tokens of context every time the server is loaded.
Does the Zhenghe — 正和支付路由与资本保全金库 MCP server require authentication?
No. We connected to Zhenghe — 正和支付路由与资本保全金库 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zhenghe — 正和支付路由与资本保全金库 MCP server still maintained?
Zhenghe — 正和支付路由与资本保全金库 is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.