BitAXE Gamma MCP Server
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"bitaxe-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# bitaxe-mcp A single-process [MCP](https://modelcontextprotocol.io/) server for monitoring and configuring [BitAXE](https://www.minebeecool.com/) Bitcoin ASIC miners. Shipped as the installable `bitaxe-mcp` distribution (`import bitaxe_mcp`) — exposes tool functions that proxy HTTP requests to miner APIs, no boilerplate, no framework weight. ## Features - **Monitor** miner stats, ASIC capabilities, system info, and WiFi networks in real time - **Configure** pools, fans, frequency/voltage, display settings, and more via generic patch tools - **Maintain** miners remotely with restart and identify functions - **Docker-ready** — multi-stage build + host-network deployment for LAN-located miners ## Architecture ``` bitaxe-mcp/ ├── src/ │ └── bitaxe_mcp/ # importable package (shipped in the wheel) │ ├── __init__.py # docstring + __version__ (from installed metadata) │ ├── config.py # MINERS_CONFIG env parser (pydantic), IP resolution, cache │ ├── client.py # _http_request() helper, _format_json, timeout constants │ ├── discovery.py # subnet detection + concurrent LAN host probing │ ├── server.py # FastMCP instance, lifespan, main() entry point │ └── tools/ # @mcp.tool() functions grouped by domain │ ├── monitor.py # status, stats, asic_info, scan_wifi (GET) │ ├── configure.py # configure, set_fan, set_frequency (PATCH) │ ├── pool.py # set_pool (PATCH) │ ├── maintenance.py # restart, identify, list_miners (POST/config) │ └── discover.py # discover (LAN scan) ├── .env.example # Example environment configuration ├── pyproject.toml # uv project manifest — deps, dev-deps, pytest config, build backend ├── tests/ │ ├── conftest.py # autouse fixtures: mock transport, seeded miners │ ├── test_config.py # config parsing and validation (8 cases) │ └── test_server.py # all 12 tool functions + error paths (40+ cases) ├── Docke…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.