pulsemcp verified Safe content atomic mcp-remote

Bitget Trading

This MCP server provides complete trading functionality for Bitget cryptocurrency exchange, built by Yury Gagarin using TypeScript with comprehensive REST API integration and WebSocket support for real-time data streaming. The implementation automatically detects spot versus futures trading contexts, offers 15+ specialized tools covering market data retrieval (prices, tickers, order books, candlestick charts), account management (balances, positions), order execution (place, cancel, query orders), and futures-specific operations (leverage setting, margin info), plus WebSocket subscriptions for live price feeds and order book updates. Features include intelligent caching with TTL expiration, exponential backoff retry logic, rate limiting protection, and robust error handling with custom exception classes, making it valuable for algorithmic trading systems, portfolio management applications, and AI assistants that need programmatic access to Bitget's spot and derivatives markets with both historical data analysis and real-time trading capabilities.

Cognium trust score

86%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: finance
Source: PulseMCP
Repository: github.com/gagarinyury/mcp-bitget-trading
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Bitget Trading from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"