BitSage MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BitSage MCP Serverlist available workers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BitSage MCP Server
MCP (Model Context Protocol) server that enables LLMs like Claude to interact with the BitSage Network for distributed compute operations.
Features
Job Management: Submit, monitor, and cancel compute jobs
Worker Discovery: List and inspect available compute workers
Proof Verification: Verify ZK proofs on-chain
Staking: Stake SAGE tokens and claim rewards
Faucet: Claim testnet tokens (Sepolia only)
Network Stats: Monitor network health and utilization
Related MCP server: RustChain + BoTTube MCP Server
Installation
npm install @bitsage/mcp-serverOr run directly with npx:
npx @bitsage/mcp-serverConfiguration
Set environment variables:
# API endpoint (optional, defaults to production)
export BITSAGE_API_URL=https://api.bitsage.network
# Starknet RPC (optional)
export STARKNET_RPC_URL=https://starknet-sepolia.public.blastapi.io
# Network: mainnet or sepolia (optional, defaults to sepolia)
export BITSAGE_NETWORK=sepoliaUsage with Claude Desktop
Add to your Claude Desktop configuration (~/.claude/claude_desktop_config.json):
{
"mcpServers": {
"bitsage": {
"command": "npx",
"args": ["@bitsage/mcp-server"],
"env": {
"BITSAGE_NETWORK": "sepolia"
}
}
}
}Available Tools
Job Management
Tool | Description |
| Submit a compute job (AI inference, ZK proof, etc.) |
| Get current status of a job |
| Cancel a pending or running job |
| List jobs with optional status filter |
Worker Management
Tool | Description |
| List available compute workers |
| Get details about a specific worker |
Proof Verification
Tool | Description |
| Get proof details by hash |
| Verify a proof on-chain |
Staking
Tool | Description |
| Stake SAGE tokens |
| Unstake SAGE tokens |
| Claim staking rewards |
| Get staking info for an address |
Faucet (Testnet only)
Tool | Description |
| Claim testnet SAGE tokens |
| Check faucet cooldown status |
ZKML Proving & Verification
Tool | Description |
| Submit a ZKML proving job (model must be loaded on prover) |
| Poll proving job status and progress |
| Get completed proof (calldata, commitments, gas estimate) |
| Check on-chain verification status for a proof or model |
Network
Tool | Description |
| Get network statistics |
ZKML Configuration
The ZKML tools connect to a prove-server instance (see libs/stwo-ml/) and the on-chain verifier contract.
# Prover server URL (default: http://localhost:8080)
export BITSAGE_PROVER_URL=http://your-gpu-server:8080
# On-chain verifier contract (default: deployed v3 on Sepolia)
export ZKML_VERIFIER_ADDRESS=0x048070fbd531a0192f3d4a37eb019ae3174600cae15e08c737982fae5d929160Example Interactions
Submit an AI Inference Job
User: Submit an AI inference job using llama-7b model with my prompt "What is the capital of France?"
Claude: I'll submit that job for you.
[Uses bitsage_submit_job tool]
The job has been submitted successfully:
- Job ID: abc123-def456
- Status: pending
- Estimated cost: 50 SAGE tokensCheck Network Status
User: How many workers are available on the BitSage network?
Claude: Let me check the network stats.
[Uses bitsage_network_stats tool]
The BitSage network currently has:
- Total workers: 150
- Active workers: 89
- Worker utilization: 59.3%
- Jobs in progress: 42
- Total jobs completed: 15,234Prove and Verify ML Inference
User: Prove the model 0xabc123 and check if it verifies on-chain.
Claude: I'll submit a proving job and track it.
[Uses bitsage_submit_zkml_proof with model_id: "0xabc123", gpu: true]
Proving job submitted:
- Job ID: d4e5f6a7-...
- Status: queued
[Uses bitsage_get_zkml_proof_status with job_id: "d4e5f6a7-..."]
Proof completed in 40.5s:
- 160 matmul sumcheck proofs
- 40 layers proven
- ~350,000 estimated gas
- 2,847 calldata felts
[Uses bitsage_verify_zkml_onchain with model_id: "0xabc123"]
On-chain status:
- Verification count: 3
- Weight commitment: 0x7f2a...Development
# Install dependencies
npm install
# Build
npm run build
# Run in development
npm run devLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bitsage-Network/bitsage-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server