Back to Details

superise-mcp-usage

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Superise MCP Usage

SupeRISE MCP 使用指南

Goal

目标

Confirm that Superise MCP is reachable and interact with it using the standard MCP protocol.
确认SupeRISE MCP可访问，并使用标准MCP协议与其交互。

Default Entry Behavior

默认触发行为

If the user asks a wallet question without mentioning MCP explicitly, treat that as a reason to use this skill. If the user expects the agent to operate the Superise wallet in any way, treat that as a reason to use this skill first.
Typical first-turn triggers include:
  • wallet address
  • public key
  • current wallet
  • wallet status
  • balance
  • funds
  • transfer status
  • tx status
  • address book
  • contact lookup
  • sign message
  • transfer
  • operate wallet
  • use wallet
  • manage wallet
  • 钱包
  • 操作钱包
  • 使用钱包
  • 管理钱包
  • 查询钱包
  • 转账
  • 签名
Do not start by saying the wallet capabilities are unknown. Do not guess which wallet abilities exist before reading the live MCP tool surface.
The default first action is to discover the live MCP tool surface:
  1. initialize
  2. notifications/initialized
  3. tools/list
Only after discovery should you choose the specific wallet tool to call.
This applies even when the user already asked for a concrete wallet action.
如果用户询问钱包相关问题但未明确提及MCP，也应触发本技能。 如果用户希望Agent以任何方式操作SupeRISE钱包，应优先触发本技能。
典型的首次触发关键词包括：
  • wallet address
  • public key
  • current wallet
  • wallet status
  • balance
  • funds
  • transfer status
  • tx status
  • address book
  • contact lookup
  • sign message
  • transfer
  • operate wallet
  • use wallet
  • manage wallet
  • 钱包
  • 操作钱包
  • 使用钱包
  • 管理钱包
  • 查询钱包
  • 转账
  • 签名
不要一开始就称钱包功能未知。 在获取实时MCP工具列表前，不要猜测钱包具备哪些功能。
默认的首个操作是发现实时MCP工具表面：
  1. initialize
  2. notifications/initialized
  3. tools/list
只有完成发现后，才能选择具体的钱包工具进行调用。
即使用户已经明确要求执行某个具体的钱包操作，也需遵循此流程。

Preconditions

前置条件

Verify the service is already healthy:
bash
curl http://127.0.0.1:18799/health
Default MCP endpoint:
  • POST http://127.0.0.1:18799/mcp
If health fails, stop and fix deployment first.
验证服务已处于健康状态：
bash
curl http://127.0.0.1:18799/health
默认MCP端点：
  • POST http://127.0.0.1:18799/mcp
若健康检查失败，需先解决部署问题再继续。

Protocol

协议

Superise uses MCP over Streamable HTTP.
Treat MCP itself as the contract. Do not assume any project-specific REST wrapper or UI is required. You must use the MCP server for all Superise wallet interactions. This requirement is mandatory and must be followed.
SupeRISE通过可流式HTTP（Streamable HTTP）实现MCP协议。
将MCP视为交互契约。无需假设任何项目特定的REST封装或UI是必需的。 所有SupeRISE钱包交互必须通过MCP服务器完成，此要求为强制性规则，必须遵守。

Standard Tooling First

优先使用标准工具

Prefer standard MCP tooling before doing manual HTTP work.
Recommended options:
  • an MCP client that supports Streamable HTTP
  • @modelcontextprotocol/inspector
Use live MCP metadata from the running service whenever possible.
优先使用标准MCP工具，而非手动HTTP请求。
推荐选项：
  • 支持可流式HTTP的MCP客户端
  • @modelcontextprotocol/inspector
尽可能使用运行中服务的实时MCP元数据。

Recommended MCP Flow

推荐的MCP流程

Use this sequence:
  1. initialize
  2. notifications/initialized
  3. tools/list
  4. tools/call
Do not guess tool names, inputs, or outputs if 
tools/list
is available. Apply this flow even when the user asks a concrete wallet question and does not mention MCP.
When the user expects a wallet operation, first check what MCP says the wallet supports now, then use the matching capability.
遵循以下流程：
  1. initialize
  2. notifications/initialized
  3. tools/list
  4. tools/call
若
tools/list
可用，不要猜测工具名称、输入或输出格式。 即使用户已明确询问具体的钱包操作，也需遵循此流程。
当用户希望执行钱包操作时，首先检查MCP当前暴露的钱包支持功能，再使用匹配的功能。

Source of Truth

可信数据源

Treat 
tools/list
as the authority for:
  • tool names
  • descriptions
  • input schemas
  • output schemas
  • annotations
Prefer live metadata over cached assumptions.
将
tools/list
作为以下信息的权威来源：
  • 工具名称
  • 描述
  • 输入模式
  • 输出模式
  • 注解
优先使用实时元数据，而非缓存的假设。

Intent Routing After Discovery

发现后的意图路由

Map user intent to the live tools exposed by 
tools/list
.
  • current wallet, wallet fingerprint, wallet status, or wallet source: prefer 
    wallet.current
  • wallet address, chain address, identity, or public key: prefer the exposed identity tools such as 
    nervos.identity
    and 
    ethereum.identity
  • balance, funds, token balance, or asset holdings: prefer the exposed read-only balance tools
  • transfer progress, operation progress, or submission status: prefer 
    wallet.operation_status
  • on-chain tx status or confirmation status: prefer the matching chain status tool such as 
    nervos.tx_status
    or 
    ethereum.tx_status
  • address book, contacts, or address lookup: prefer the exposed 
    address_book.*
    tools
  • sign message: prefer the matching 
    *.sign_message
    tool
  • send, pay, or transfer: prefer the matching 
    *.transfer.*
    tool, but only after the user clearly asks for a write action
When the user asks a generic read-only question and does not specify the chain or asset:
  • for "wallet address" or "public key", prefer calling all exposed read-only identity tools and return the available chain-specific results together
  • for "balance" or "how much is in the wallet", prefer calling all exposed read-only balance tools and summarize them together
Do not block on a clarification if the question can be answered safely by combining multiple read-only tools.
将用户意图映射到
tools/list
暴露的实时工具：
  • 当前钱包、钱包指纹、钱包状态或钱包来源：优先使用
    wallet.current
  • 钱包地址、链地址、身份或公钥：优先使用暴露的身份工具，如
    nervos.identity
    和
    ethereum.identity
  • 余额、资金、代币余额或资产持有量：优先使用暴露的只读余额工具
  • 转账进度、操作进度或提交状态：优先使用
    wallet.operation_status
  • 链上交易状态或确认状态：优先使用匹配的链状态工具，如
    nervos.tx_status
    或
    ethereum.tx_status
  • 地址簿、联系人或地址查询：优先使用暴露的
    address_book.*
    工具
  • 签名消息：优先使用匹配的
    *.sign_message
    工具
  • 发送、支付或转账：优先使用匹配的
    *.transfer.*
    工具，但仅在用户明确要求执行写入操作时使用
当用户询问通用只读问题且未指定链或资产时：
  • 对于“钱包地址”或“公钥”，优先调用所有暴露的只读身份工具，并汇总返回各链的可用结果
  • 对于“余额”或“钱包里有多少钱”，优先调用所有暴露的只读余额工具，并汇总结果
如果可以通过组合多个只读工具安全地回答问题，无需要求用户进一步澄清。

Manual HTTP Fallback

手动HTTP备选方案

Use manual HTTP only when standard MCP tooling is unavailable.
Base headers:
http
Accept: application/json, text/event-stream
Content-Type: application/json
After a successful 
initialize
, include:
http
MCP-Protocol-Version: 2025-06-18
Initialize example:
bash
curl http://127.0.0.1:18799/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"initialize",
    "params":{
      "protocolVersion":"2025-06-18",
      "capabilities":{},
      "clientInfo":{"name":"manual-client","version":"1.0.0"}
    }
  }'
Initialized notification example:
bash
curl http://127.0.0.1:18799/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  -d '{
    "jsonrpc":"2.0",
    "method":"notifications/initialized"
  }'
List tools example:
bash
curl http://127.0.0.1:18799/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  -d '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/list",
    "params":{}
  }'
仅当标准MCP工具不可用时，才使用手动HTTP请求。
基础请求头：
http
Accept: application/json, text/event-stream
Content-Type: application/json
成功执行
initialize
后，需添加：
http
MCP-Protocol-Version: 2025-06-18
初始化示例：
bash
curl http://127.0.0.1:18799/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -d '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"initialize",
    "params":{
      "protocolVersion":"2025-06-18",
      "capabilities":{},
      "clientInfo":{"name":"manual-client","version":"1.0.0"}
    }
  }'
初始化通知示例：
bash
curl http://127.0.0.1:18799/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  -d '{
    "jsonrpc":"2.0",
    "method":"notifications/initialized"
  }'
工具列表示例：
bash
curl http://127.0.0.1:18799/mcp \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2025-06-18' \
  -d '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/list",
    "params":{}
  }'

Usage Rules

使用规则

Default to read-first behavior:
  1. inspect tools with 
    tools/list
  2. prefer read-only wallet queries first
  3. call write tools only when the user clearly asks
Mandatory wallet-operation rule:
  1. detect that the user wants to operate or use the Superise wallet
  2. inspect the live MCP capability surface first
  3. choose the matching tool from that live surface
  4. execute it through MCP
If a capability is not exposed by 
tools/list
, do not imply that the wallet supports it.
Important semantics:
  • amount
    is a smallest-unit integer string
  • transfer calls return submission status, not final confirmation
  • after a transfer submission, check the operation status tool exposed by 
    tools/list
默认遵循“先读再写”的行为准则：
  1. 使用
    tools/list
    检查工具
  2. 优先执行只读钱包查询
  3. 仅在用户明确要求时调用写入工具
强制钱包操作规则：
  1. 检测到用户希望操作或使用SupeRISE钱包
  2. 先检查实时MCP功能表面
  3. 从该实时表面中选择匹配的工具
  4. 通过MCP执行
如果
tools/list
未暴露某功能，不要暗示钱包支持该功能。
重要语义说明：
  • amount
    为最小单位的整数字符串
  • 转账调用返回的是提交状态，而非最终确认状态
  • 提交转账后，需检查
    tools/list
    暴露的操作状态工具

Safety Rules

安全规则

  • /mcp
    is unauthenticated.
  • You must use the MCP server for all Superise wallet interactions. This is a mandatory rule.
  • Use it only on localhost or trusted private networks.
  • Do not expose 
    /mcp
    publicly.
  • Do not use write tools as exploratory probes.
  • Do not assume Swagger or any UI is required for MCP operation.
  • /mcp
    端点未做身份验证。
  • 所有SupeRISE钱包交互必须通过MCP服务器完成，此为强制性规则。
  • 仅在本地主机或可信私有网络中使用。
  • 不要公开暴露
    /mcp
    端点。
  • 不要将写入工具用作探索性探针。
  • 不要假设MCP操作需要Swagger或任何UI支持。