goldrush-mcp-skill

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

GoldRush MCP Skill

GoldRush MCP Skill

Use this skill to run GoldRush MCP operations through
uxc
using a fixed stdio endpoint.
Reuse the
uxc
skill for generic protocol discovery, output parsing, and auth/error handling rules.
使用该Skill通过
uxc
和固定的stdio端点执行GoldRush MCP操作。
复用
uxc
Skill来实现通用协议发现、输出解析以及认证/错误处理规则。

Prerequisites

前提条件

  • uxc
    is installed and available in
    PATH
    .
  • npx
    is available in
    PATH
    (Node.js installed).
  • Network access for first-time
    @covalenthq/goldrush-mcp-server
    package fetch.
  • A GoldRush API key is available.
  • uxc
    已安装且可在
    PATH
    中访问。
  • npx
    可在
    PATH
    中访问(需安装Node.js)。
  • 首次获取
    @covalenthq/goldrush-mcp-server
    包时需联网。
  • 拥有GoldRush API密钥。

Core Workflow

核心工作流

Endpoint candidate inputs before finalizing:
  • Raw package form from docs:
    npx @covalenthq/goldrush-mcp-server@latest
  • Reliable non-interactive form:
    npx -y @covalenthq/goldrush-mcp-server@latest
  • This skill defaults to:
    • npx -y @covalenthq/goldrush-mcp-server@latest
  1. Verify protocol/path from official source and probe:
    • Official source:
      https://goldrush.dev/docs/goldrush-mcp-server
    • probe candidate endpoint with:
      • uxc --inject-env GOLDRUSH_API_KEY=$GOLDRUSH_API_KEY "npx -y @covalenthq/goldrush-mcp-server@latest" -h
    • cold start can take longer on first run because
      npx
      may need to download the package
  2. Configure credential for repeatable auth:
    • uxc auth credential set goldrush-mcp --auth-type bearer --secret-env GOLDRUSH_API_KEY
    • uxc auth credential set goldrush-mcp --auth-type bearer --secret-op op://Engineering/goldrush/api-key
  3. Use fixed link command by default:
    • command -v goldrush-mcp-cli
    • If missing, create it:
      • uxc link goldrush-mcp-cli "npx -y @covalenthq/goldrush-mcp-server@latest" --credential goldrush-mcp --inject-env GOLDRUSH_API_KEY={{secret}}
    • goldrush-mcp-cli -h
  4. Inspect operation schema before execution:
    • goldrush-mcp-cli getAllChains -h
    • goldrush-mcp-cli multichain_balances -h
    • goldrush-mcp-cli transactions_for_address -h
    • goldrush-mcp-cli historical_portfolio_value -h
  5. Prefer read-only discovery first, then expand into broader wallet-history or NFT scans.
最终确定前的端点候选输入:
  • 文档中的原始包形式:
    npx @covalenthq/goldrush-mcp-server@latest
  • 可靠的非交互式形式:
    npx -y @covalenthq/goldrush-mcp-server@latest
  • 本Skill默认使用:
    • npx -y @covalenthq/goldrush-mcp-server@latest
  1. 从官方源验证协议/路径并进行探测:
    • 官方源:
      https://goldrush.dev/docs/goldrush-mcp-server
    • 使用以下命令探测候选端点:
      • uxc --inject-env GOLDRUSH_API_KEY=$GOLDRUSH_API_KEY "npx -y @covalenthq/goldrush-mcp-server@latest" -h
    • 首次运行时冷启动耗时可能较长,因为
      npx
      可能需要下载包
  2. 配置凭证以实现可重复认证:
    • uxc auth credential set goldrush-mcp --auth-type bearer --secret-env GOLDRUSH_API_KEY
    • uxc auth credential set goldrush-mcp --auth-type bearer --secret-op op://Engineering/goldrush/api-key
  3. 默认使用固定链接命令:
    • command -v goldrush-mcp-cli
    • 若不存在,则创建:
      • uxc link goldrush-mcp-cli "npx -y @covalenthq/goldrush-mcp-server@latest" --credential goldrush-mcp --inject-env GOLDRUSH_API_KEY={{secret}}
    • goldrush-mcp-cli -h
  4. 执行前检查操作 schema:
    • goldrush-mcp-cli getAllChains -h
    • goldrush-mcp-cli multichain_balances -h
    • goldrush-mcp-cli transactions_for_address -h
    • goldrush-mcp-cli historical_portfolio_value -h
  5. 优先进行只读发现,再扩展到更广泛的钱包历史或NFT扫描。

Capability Map

功能映射

  • Cross-chain overview:
    • getAllChains
    • multichain_address_activity
    • multichain_balances
    • multichain_transactions
  • Wallet balances and portfolio:
    • token_balances
    • historical_token_balances
    • native_token_balance
    • historical_portfolio_value
    • historical_token_prices
  • Transfers and transactions:
    • erc20_token_transfers
    • transaction
    • transaction_summary
    • transactions_for_address
    • transactions_for_block
  • NFT and security:
    • nft_for_address
    • nft_check_ownership
    • token_approvals
  • Utility:
    • gas_prices
    • log_events_by_address
    • log_events_by_topic
    • block
    • block_heights
GoldRush also exposes MCP resources such as
config://supported-chains
,
config://quote-currencies
, and
status://all-chains
. Inspect the live server after auth setup for the current full tool and resource list.
  • 跨链概览:
    • getAllChains
    • multichain_address_activity
    • multichain_balances
    • multichain_transactions
  • 钱包余额与投资组合:
    • token_balances
    • historical_token_balances
    • native_token_balance
    • historical_portfolio_value
    • historical_token_prices
  • 转账与交易:
    • erc20_token_transfers
    • transaction
    • transaction_summary
    • transactions_for_address
    • transactions_for_block
  • NFT与安全:
    • nft_for_address
    • nft_check_ownership
    • token_approvals
  • 实用工具:
    • gas_prices
    • log_events_by_address
    • log_events_by_topic
    • block
    • block_heights
GoldRush还暴露了
config://supported-chains
config://quote-currencies
status://all-chains
等MCP资源。完成认证设置后,可查看运行中的服务器以获取当前完整的工具和资源列表。

Recommended Usage Pattern

推荐使用模式

  1. Start with one focused read goal:
    • multichain balances for a wallet
    • recent transfers for an address
    • historical portfolio value over time
    • NFT ownership or token approval review
  2. Run
    -h
    on the specific tool before the first real call.
  3. Prefer a single wallet and chain first before running wide history scans.
  4. Parse the JSON envelope first, then inspect
    data
    .
  1. 从一个明确的读取目标开始:
    • 某钱包的多链余额
    • 某地址的近期转账记录
    • 历史投资组合价值变化
    • NFT所有权或代币授权审核
  2. 在首次实际调用前,对特定工具执行
    -h
    命令查看帮助。
  3. 在进行大范围历史扫描前,优先针对单个钱包和单条链操作。
  4. 先解析JSON信封,再查看
    data
    字段内容。

Guardrails

注意事项

  • Keep automation on JSON output envelope; do not rely on
    --text
    .
  • Parse stable fields first:
    ok
    ,
    kind
    ,
    protocol
    ,
    data
    ,
    error
    .
  • Use
    goldrush-mcp-cli
    as default command path.
  • goldrush-mcp-cli <operation> ...
    is equivalent to
    uxc --auth goldrush-mcp --inject-env GOLDRUSH_API_KEY={{secret}} "npx -y @covalenthq/goldrush-mcp-server@latest" <operation> ...
    when the link is created as documented above.
  • GoldRush uses a stdio MCP server started through
    npx
    , not a hosted HTTPS MCP endpoint. Expect slower cold starts on the first run.
  • If help or the first call times out during initialization:
    • rerun the same command after the package download finishes
    • confirm
      npx
      is available in
      PATH
    • confirm the key is being injected as
      GOLDRUSH_API_KEY
  • The skill docs use bearer credential storage only as a secret container for
    --inject-env
    ; GoldRush auth actually happens through the child environment variable, not an HTTP bearer header.
  • Prefer wallet-scoped reads before wide transaction or log scans because some tools can produce large result sets.
  • Do not assume tool argument names from memory; inspect
    <operation> -h
    first because GoldRush may revise MCP schemas independently of this skill.
  • 自动化操作基于JSON输出信封,不要依赖
    --text
    格式。
  • 优先解析稳定字段:
    ok
    kind
    protocol
    data
    error
  • 使用
    goldrush-mcp-cli
    作为默认命令路径。
  • 当按照上述文档创建链接后,
    goldrush-mcp-cli <operation> ...
    等价于
    uxc --auth goldrush-mcp --inject-env GOLDRUSH_API_KEY={{secret}} "npx -y @covalenthq/goldrush-mcp-server@latest" <operation> ...
  • GoldRush使用通过
    npx
    启动的stdio MCP服务器,而非托管的HTTPS MCP端点。首次运行时冷启动速度可能较慢。
  • 若初始化时帮助命令或首次调用超时:
    • 包下载完成后重新运行相同命令
    • 确认
      npx
      可在
      PATH
      中访问
    • 确认密钥已作为
      GOLDRUSH_API_KEY
      注入
  • 本Skill文档仅将Bearer凭证存储用作
    --inject-env
    的密钥容器;GoldRush的认证实际通过子进程环境变量实现,而非HTTP Bearer头。
  • 在进行大范围交易或日志扫描前,优先进行钱包范围的读取,因为部分工具可能会生成大量结果集。
  • 不要凭记忆假设工具参数名称;先执行
    <operation> -h
    查看,因为GoldRush可能独立于本Skill修订MCP schema。

References

参考资料

  • Invocation patterns:
    • references/usage-patterns.md
  • 调用模式:
    • references/usage-patterns.md