MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
MCPpedia last refreshed this data
io.gainium/gainium-mcp is an MCP server that MCP server for Gainium — manage trading bots, deals, and balances via AI assistants. Its tool list has not been published yet over http and stdio, requires no API key, and scores 85/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-gainium-gainium-mcp": {
"args": [
"-y",
"gainium-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for Gainium — manage trading bots, deals, and balances via AI assistants
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked gainium-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml / finance
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
Open source device layer for AI agents: control mobile, web, TV, and desktop apps over MCP
MCP Security Weekly
Get CVE alerts and security updates for io.gainium/gainium-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server for Gainium — the crypto trading bot platform. Lets AI assistants manage your bots, deals, balances, and more through a standard MCP interface.
Detailed setup and connection documentation is available in docs/using-gainium-mcp.md.
Go to Gainium API Settings and create an API key pair.
Add this to your MCP configuration (VS Code, Claude Desktop, etc.):
{
"gainium-mcp": {
"command": "npx",
"args": ["-y", "gainium-mcp"],
"env": {
"GAINIUM_API_KEY": "<your-api-key>",
"GAINIUM_API_SECRET": "<your-api-secret>"
}
}
}
That's it. The server starts automatically when your AI assistant needs it.
This local stdio mode uses GAINIUM_API_KEY and GAINIUM_API_SECRET from the server process environment.
| Variable | Required | Default | Description |
|---|---|---|---|
GAINIUM_API_KEY | Yes | — | Your Gainium API public key |
GAINIUM_API_SECRET | Yes | — | Your Gainium API secret |
GAINIUM_API_BASE_URL | No | https://api.gainium.io | API base URL |
GAINIUM_MCP_TRANSPORT | No | stdio | Transport mode: stdio, http, streamable-http, sse, or http-sse |
GAINIUM_MCP_HOST | No | 127.0.0.1 | Bind host for HTTP mode |
GAINIUM_MCP_PORT | No | 3000 | Bind port for HTTP mode |
GAINIUM_MCP_ALLOWED_HOSTS | No | — | Comma-separated hostnames (optionally host:port) accepted in the Host/Origin headers. In HTTP mode with env credentials and no OAuth, only loopback, IP-literal and these hosts are served (DNS rebinding protection) |
GAINIUM_MCP_HTTP_PATH | No | /mcp | Streamable HTTP endpoint path |
GAINIUM_MCP_SSE_PATH | No | /sse | Deprecated SSE GET endpoint path |
GAINIUM_MCP_MESSAGES_PATH | No | /messages | Deprecated SSE POST endpoint path |
GAINIUM_OAUTH_ISSUER | No | — | Authorization-server base URL. Setting this (with MCP_INTROSPECTION_SECRET, in HTTP mode) enables OAuth protected-resource mode |
GAINIUM_INTROSPECTION_URL | No | <issuer>/oauth/introspect | Token introspection endpoint |
MCP_INTROSPECTION_SECRET | No | — | Shared secret presented to the introspection endpoint (must match the auth server) |
GAINIUM_MCP_PUBLIC_URL | No | derived from request | Public base URL used in the protected-resource metadata |
OPENAI_APPS_CHALLENGE_TOKEN | No | — | When set, served as plain text at /.well-known/openai-apps-challenge for OpenAI Apps domain verification |
gainium-mcp supports three deployment models:
GAINIUM_API_KEY and GAINIUM_API_SECRET from env vars.Authorization: Bearer <token>. See OAuth 2.1 hosted mode below.X-API-Key and X-API-Secret headers so one shared server can serve many users.In header/stdio mode, request headers take priority, falling back to GAINIUM_API_KEY / GAINIUM_API_SECRET. When OAuth mode is enabled, the Bearer token is required and the X-API-Key/X-API-Secret headers are ignored.
This is the mode used for the public https://mcp.gainium.io/mcp endpoint and the Anthropic Claude connector directory (which requires OAuth and forbids API-key headers).
Enable it by setting, in HTTP mode:
export GAINIUM_MCP_TRANSPORT=http
export GAINIUM_OAUTH_ISSUER=https://app.gainium.io # Gainium authorization server
export MCP_INTROSPECTION_SECRET=<shared-secret> # must match the auth server
export GAINIUM_MCP_PUB
... [View full README on GitHub](https://github.com/gainium/gainium-mcp#readme)