Minerstat for AI agents
Minerstat is a crypto mining monitoring platform that tracks mining hardware, pools, and worker performance across a distributed mining operation. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Minerstat.
Check a worker's activity
Look up a specific mining worker's uptime and hash rate, a read-only status check.
Pull coin performance data
Check profitability data for a coin before deciding on a mining configuration.
Review pool performance
Pull pool performance data to compare options before deciding whether to switch a worker's mining pool.
5 Minerstat actions, graded by risk.
Every Minerstat action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- minerstat.get_coins_dataGet Coins Data
- minerstat.get_pools_dataGet Pools Data
- minerstat.get_worker_dataGet Worker Data
- minerstat.get_hardware_dataGet Hardware Data
- minerstat.get_worker_activityGet Worker Activity
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Minerstat in three steps.
- 01Your users connect MinerstatThey add their Minerstat api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Minerstat through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('minerstat', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Minerstat connects.
Users add their Minerstat api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Minerstat connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Minerstat from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Minerstat and Arc0, answered.
Can I use Minerstat with Claude, ChatGPT or Cursor?
Yes. Connect Minerstat to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Minerstat actions you allow.
How do users connect Minerstat?
Users add their Minerstat api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Minerstat actions can my agent take?
5 in total: 5 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Minerstat?
Yes. Allow read actions and deny writes in the Minerstat policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Minerstat too?
Yes. The same Minerstat connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Minerstat into your agent.
Your users connect Minerstat once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan