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.

Prerequisites

• - uxc is installed and available in PATH.
• INLINECODE4 is available in PATH (Node.js installed).
• Network access for first-time @covalenthq/goldrush-mcp-server package fetch.
• A GoldRush API key is available.

Core Workflow

Endpoint candidate inputs before finalizing:

• - Raw package form from docs: INLINECODE7
• Reliable non-interactive form: INLINECODE8
• This skill defaults to:

1. 1. Verify protocol/path from official source and probe:

1. 2. Configure credential for repeatable auth:

1. 3. Use fixed link command by default:

1. 4. Inspect operation schema before execution:

1. 5. Prefer read-only discovery first, then expand into broader wallet-history or NFT scans.

Capability Map

• - Cross-chain overview:

• - Wallet balances and portfolio:

• - Transfers and transactions:

• - NFT and security:

• - Utility:

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.

Recommended Usage Pattern

1. 1. Start with one focused read goal:

1. 2. Run -h on the specific tool before the first real call.
2. Prefer a single wallet and chain first before running wide history scans.
3. Parse the JSON envelope first, then inspect 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.
• INLINECODE56 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:

• - 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.

References

• - Invocation patterns: