# Zhenghe — 正和支付路由与资本保全金库 (remote · mcp.zheng-he.top)

Base 主网去中心化支付路由+金库：查 NAV、构造路由支付 calldata、金库存取、绑定引路人分账。存款安全·引路人激励·消费即升值，全部链上可核验。

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.zheng-he.top`: 65/100 (this document), [markdown](https://verifymcp.io/servers/top-zheng-he-zhenghe-mcp/mcp.md), [page](https://verifymcp.io/servers/top-zheng-he-zhenghe-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.zheng-he.top/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http top-zheng-he-zhenghe-mcp https://mcp.zheng-he.top/mcp
```

### Codex

```toml
[mcp_servers.top-zheng-he-zhenghe-mcp]
url = "https://mcp.zheng-he.top/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "top-zheng-he-zhenghe-mcp": {
      "type": "remote",
      "url": "https://mcp.zheng-he.top/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add top-zheng-he-zhenghe-mcp --url https://mcp.zheng-he.top/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  top-zheng-he-zhenghe-mcp:
    url: "https://mcp.zheng-he.top/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 65, +1)

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

### 2026-07-31 (score 64, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62)

First indexed and scored.

## MCP tools (4)

### `nav_query` (~84 tokens)

查询正和金库实时状态：NAV（净值）、金库 USDC 总资产、LOVE 总份额、累计溢价。只读，无需任何授权。传入 address 可同时查该地址的 LOVE/USDC 余额与浮盈。

Input parameters:

- `address` (string): （可选）要查余额的钱包地址 0x…

### `zhenghe_route` (~225 tokens)

构造一笔正和路由支付（消费入口）。返回签名就绪的 approve+pay calldata，调用方本地签名上链即完成原子正和支付：商户收 USDC + 捐赠注入金库 + 引路人分账 + NAV 抬升。路由决策：USDC 够→直接付；USDC 不足但 LOVE×NAV 够→赎回 LOVE 付；都不够→返回缺口。私钥永不经过服务器。

Input parameters:

- `amount` (number, required): 支付金额（USDC，必填）
- `leader` (string): 引路人地址（可选，未绑定时可自引自收）
- `merchant` (string, required): 收款商户地址 0x…（必填）
- `payer` (string): 付款方地址（可选，传入则按真实余额做路由决策）
- `ref` (string): 订单引用（可选，将 keccak 为 bytes32）

### `vault_action` (~140 tokens)

正和金库操作。action=deposit：USDC→LOVE（返回 approve+deposit calldata）；action=withdraw：LOVE→USDC（返回 redeem calldata）；action=balance：查 LOVE 余额+NAV+浮盈（只读）。金库无 owner、无管理函数，NAV 单调增长——存款安全由合约字节码保证，可自验。

Input parameters:

- `action` (string, required)
- `address` (string, required): 操作地址 0x…（deposit/withdraw 的接收方，balance 的查询方）
- `amount` (number): deposit=USDC 数量；withdraw=LOVE 数量

### `affiliate_bind` (~138 tokens)

绑定引路人（一次性、永久、链上不可改）。返回 bindReferrer calldata，签名上链即完成绑定。此后该地址每笔路由消费的 6bps USDC 立即分给引路人，商户捐赠 LOVE 的 20% 同样分账，原子结算。任何 Agent 都可以成为引路人推广正和并永久获取分成。

Input parameters:

- `binder` (string): 被绑定地址 0x…（calldata 的 from，仅用于展示）
- `leader` (string, required): 引路人地址 0x…（必填）

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/top-zheng-he-zhenghe-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 64
- 2026-07-31: 64
- 2026-07-30: 62

## Links

- Remote endpoint: https://mcp.zheng-he.top/mcp
- Repository: https://github.com/batcatchina/zhenghe-mcp
- Changelog RSS feed: https://verifymcp.io/servers/top-zheng-he-zhenghe-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/top-zheng-he-zhenghe-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/top-zheng-he-zhenghe-mcp/mcp