The public half is harmless — prices, book, exchange status — and useful on its own. The trading half is not: the key it holds can create and cancel real orders, and the same conversational convenience that makes an order easy to place makes it easy to place by accident. The README asks you to confirm amount and rate every time, which is the right instinct. If you only want market data, issue a key without trading permission.
A Go MCP server for the Coincheck cryptocurrency exchange, covering three groups of its API: the public market endpoints, the account endpoints and the trading endpoints. It installs through make targets, one of which writes the Claude Desktop entry for you.
- Public market data: prices, trade history, the order book, exchange status and an order-rate calculation
- Account reads: balances and account information
- Trading: order history, creating an order, cancelling one, reading an order's details, and listing orders that have not filled
- Credentials kept out of the repository — the config file holding the key and secret is excluded from git by default
A Coincheck API key and secret, taken from the exchange's API settings page and written into `config/coincheck_config.json` — `make setup` creates the file for you to fill in. Build with `make all`; `make deploy` copies the client entry into place, after which the client launches `coincheck-mcp --config /path/to/config/coincheck_config.json`. The repository ships a `go.mod`, so a Go toolchain is what builds it. `make test` and `make status` check the binary and the current state. Setup documentation is in Japanese.