M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionHummingbot MCP ServerConnect Hummingbot via MCP for automated multi-exchange crypto tradingGitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS51 / 100 · D76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions6 / 2014 / 20
Maintenance10 / 2018 / 20
Documentation14 / 2017 / 20
Setup experience12 / 2014 / 20
Best for
  • Users already running Hummingbot API who want AI-client control of trading
  • Crypto traders comfortable with Docker/uv configuration
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users without Hummingbot or a running API server
  • Beginners without trading background who cannot absorb automated-trading risk
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Requires Hummingbot API username and password (HUMMINGBOT_USERNAME, HUMMINGBOT_PASSWORD)
  • Requires a reachable Hummingbot API URL (HUMMINGBOT_API_URL)
  • Docker deployment mounts ~/.hummingbot_mcp to persist configuration
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • The server can place real trade orders; misconfiguration can lead to financial loss
  • API credentials are stored in environment variables and .env files and must be protected
  • Connecting to a wrong URL or exposing the API publicly introduces security risk
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsClaude Code, Gemini CLIClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools115