rgo-trading-api
by bhdhiman
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RGO_WS_URL | Yes | Realtime WebSocket URL | |
| RGO_LICENSE_ID | Yes | Your license id | |
| RGO_CLIENT_BASE | Yes | Client API base URL, e.g. https://api.YOUR_DOMAIN:6017/clientapi | |
| RGO_API_PASSWORD | Yes | Header credentials for order writes | |
| RGO_API_USERNAME | Yes | Header credentials for order writes | |
| RGO_ALLOW_TRADING | No | Set to true to enable REAL order placement/update/deletion | false |
| RGO_DEALER_PASSWORD | Yes | Dealer login password | |
| RGO_DEALER_USERNAME | Yes | Dealer login (for the read JWT) | |
| RGO_DEALER_BASE_READ | Yes | Dealer read base URL (e.g. port 9016) | |
| RGO_DEALER_BASE_WRITE | Yes | Dealer write base URL (may use a different port, e.g. 6016) |
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/bhdhiman/rgo-trading-api'
If you have feedback or need assistance with the MCP directory API, please join our Discord server