官方说明7 个来源MCP 服务8 天前
Gainium/gainium-mcp
Manage Gainium DCA, Combo and Grid trading
在 GitHub 查看 ↗直链 · 无中转页
配置模板（请按你的客户端调整）
claude mcp add gainium-mcp -- npx -y gainium-mcp
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 2 ★ · Gainium/gainium-mcp · 取自该仓库的 GitHub 页面 · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
- 评分构成
- 综合分 703 · 2 ★ · 7 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
Gainium/gainium-mcp；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
gainium-mcp
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
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.
Quick Start
1. Get your API keys
Go to Gainium API Settings and create an API key pair.
2. Add to your MCP client
Add this to your MCP configuration (VS Code, Claude Desktop, etc.):
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.
Environment Variables
| 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_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 | /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 |
Authentication Modes
gainium-mcp supports three deployment models:
- **Local stdio mode:** the MCP server reads GAINIUM_API_KEY and GAINIUM_API_SECRET from env vars.
- **OAuth 2.1 hosted mode (recommended for hosted/public):** the server acts as an OAuth protected resource. Clients (e.g. the Claude connector) obtain an access token from the Gainium authorization server and send it as Authorization: Bearer . See OAuth 2.1 hosted mode below.
- **Header hosted mode (legacy/self-hosted):** each request sends 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.
OAuth 2.1 hosted mode
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:
When enabled, the server:
1. Serves **OAuth Protected Resource Metadata** (RFC 9728) at
/.well-known/oauth-protected-resource and /.well-known/oauth-protected-resource/mcp,
advertising the authorization server.
2. Rejects unauthenticated MCP requests with **401 Unauthorized** and a
WWW-Authenticate: Bearer resource_metadata="…" header, so clients can discover
Detailed setup and connection documentation is available in docs/using-gainium-mcp.md.
Quick Start
1. Get your API keys
Go to Gainium API Settings and create an API key pair.
2. Add to your MCP client
Add this to your MCP configuration (VS Code, Claude Desktop, etc.):
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.
Environment Variables
| 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_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 | /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 |
Authentication Modes
gainium-mcp supports three deployment models:
- **Local stdio mode:** the MCP server reads GAINIUM_API_KEY and GAINIUM_API_SECRET from env vars.
- **OAuth 2.1 hosted mode (recommended for hosted/public):** the server acts as an OAuth protected resource. Clients (e.g. the Claude connector) obtain an access token from the Gainium authorization server and send it as Authorization: Bearer . See OAuth 2.1 hosted mode below.
- **Header hosted mode (legacy/self-hosted):** each request sends 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.
OAuth 2.1 hosted mode
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:
When enabled, the server:
1. Serves **OAuth Protected Resource Metadata** (RFC 9728) at
/.well-known/oauth-protected-resource and /.well-known/oauth-protected-resource/mcp,
advertising the authorization server.
2. Rejects unauthenticated MCP requests with **401 Unauthorized** and a
WWW-Authenticate: Bearer resource_metadata="…" header, so clients can discover
- 来源
- awesome · https://github.com/Gainium/gainium-mcp
- 按领域浏览
- MCP 服务
- Traction
- 2 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。