refinore-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REFINORE_API_KEY | Yes | Your refinORE API key (starts with rsk_) | |
| REFINORE_API_URL | No | API base URL (for custom deployments) | https://automine.refinore.com/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_infoA | Get your refinORE account info including Solana wallet address and deposit instructions. Call this first to discover your wallet. |
| start_miningB | Start a new ORE mining session on refinORE. Deploys SOL/USDC/ORE across squares on the mining grid. Configure amount, number of squares, token, risk tolerance, and tile selection strategy. |
| stop_miningA | Stop an active ORE mining session. Optionally specify a session ID, or stop the current active session. |
| get_mining_sessionB | Get the status of your current active mining session, including stats and current round info. |
| get_mining_historyC | Get your past mining rounds history. Returns an array of completed mining rounds with results and earnings. |
| get_balancesB | Get wallet token balances including SOL, ORE, USDC, stORE, and SKR for a given Solana wallet address. |
| get_rewardsC | Get unclaimed rewards for a wallet — includes unclaimed SOL, unrefined ORE, and bonus ORE. |
| get_current_roundA | Get the current mining round info — round number, time remaining, total deployed, motherlode, and expected value. This is a public endpoint (no auth required). |
| list_strategiesA | List all your saved auto-mining strategies. Strategies define reusable mining configurations. |
| create_strategyB | Create a new auto-mining strategy with a name and mining parameters. Strategies can be started later with start_strategy. |
| start_strategyB | Start mining using a saved strategy. Launches an auto-mining session with the strategy's predefined parameters. |
| get_staking_infoC | Get staking information for a wallet — stORE balance, current APR, and pending staking rewards. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, create_strategy defines a new strategy, start_strategy launches it, and start_mining initiates a manual session, while get_* tools each target specific data types like balances, history, or rewards. The descriptions clearly differentiate overlapping concepts like strategies vs. sessions.
Tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly. All tools start with a clear action verb (create, get, list, start, stop) followed by a specific noun, making the set predictable and readable. There are no deviations in naming conventions.
With 12 tools, the count is well-scoped for the refinORE mining domain. Each tool earns its place by covering distinct aspects like account setup, mining operations, strategy management, and data retrieval, without feeling bloated or sparse. This aligns with typical server scopes of 3-15 tools.
The tool surface provides complete CRUD/lifecycle coverage for the mining domain. It includes account discovery (get_account_info), mining initiation and termination (start_mining, stop_mining), strategy management (create_strategy, list_strategies, start_strategy), and comprehensive data retrieval (balances, history, rewards, staking). No obvious gaps exist that would hinder agent workflows.