BitSage MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITSAGE_API_URL | No | API endpoint for BitSage (optional, defaults to production) | https://api.bitsage.network |
| BITSAGE_NETWORK | No | Network to use: mainnet or sepolia (optional, defaults to sepolia) | sepolia |
| STARKNET_RPC_URL | No | Starknet RPC URL (optional) | https://starknet-sepolia.public.blastapi.io |
| BITSAGE_PROVER_URL | No | Prover server URL for ZKML (optional, defaults to http://localhost:8080) | http://localhost:8080 |
| ZKML_VERIFIER_ADDRESS | No | On-chain verifier contract address for ZKML (optional, defaults to deployed v3 on Sepolia) | 0x048070fbd531a0192f3d4a37eb019ae3174600cae15e08c737982fae5d929160 |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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