ZBS Index What actually exists in applied AI, with the source next to it

mcp server

Zhenghe — 正和支付路由与资本保全金库

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

Description as published by the maintainer. Source

  • version 2.0.1
  • active

active — Registry entry last updated 2026-07-30.

What this server can do

4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

affiliate_bind(binder, leader)
绑定引路人(一次性、永久、链上不可改)。返回 bindReferrer calldata,签名上链即完成绑定。此后该地址每笔路由消费的 6bps USDC 立即分给引路人,商户捐赠 LOVE 的 20% 同样分账,原子结算。任何 Agent 都可以成为引路人推广正和并永久获取分成。 Required: leader.
nav_query(address)
查询正和金库实时状态:NAV(净值)、金库 USDC 总资产、LOVE 总份额、累计溢价。只读,无需任何授权。传入 address 可同时查该地址的 LOVE/USDC 余额与浮盈。
vault_action(action, amount, address)
正和金库操作。action=deposit:USDC→LOVE(返回 approve+deposit calldata);action=withdraw:LOVE→USDC(返回 redeem calldata);action=balance:查 LOVE 余额+NAV+浮盈(只读)。金库无 owner、无管理函数,NAV 单调增长——存款安全由合约字节码保证,可自验。 Required: action, address.
zhenghe_route(ref, payer, amount, leader, merchant)
构造一笔正和路由支付(消费入口)。返回签名就绪的 approve+pay calldata,调用方本地签名上链即完成原子正和支付:商户收 USDC + 捐赠注入金库 + 引路人分账 + NAV 抬升。路由决策:USDC 够→直接付;USDC 不足但 LOVE×NAV 够→赎回 LOVE 付;都不够→返回缺口。私钥永不经过服务器。 Required: merchant, amount.

Last successful function declaration observed on . Source: https://mcp.zheng-he.top/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://mcp.zheng-he.top/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 2.0.1 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-07-30 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-07-30 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 4 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe mcp.zheng-he.top
mcp endpoint status ok The server listed 4 functions when asked. as of probe mcp.zheng-he.top

Where to get it

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://mcp.zheng-he.top/mcp — mcp.zheng-he.top, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.