Command surface for the Hunto platform — version 351b19e. A single static binary; no runtime dependencies.
| Platform | Size | SHA-256 |
|---|---|---|
| RHEL / Fedora · arm64 · .rpm hunto-0.0.0+351b19e-1.aarch64.rpm | 3.4M | 80f0678eb4999fa5… |
| RHEL / Fedora · x86_64 · .rpm hunto-0.0.0+351b19e-1.x86_64.rpm | 3.8M | 28f67bf64ad24a24… |
| Debian / Ubuntu · x86_64 · .deb hunto_0.0.0+351b19e-1_amd64.deb | 3.7M | 7683acb6f44eb5b8… |
| Debian / Ubuntu · arm64 · .deb hunto_0.0.0+351b19e-1_arm64.deb | 3.3M | fd53fb31ed1b839e… |
| macOS · Intel · tar.gz hunto_351b19e_darwin_amd64.tar.gz | 3.6M | 883aed0d310b57b1… |
| macOS · Apple Silicon · tar.gz hunto_351b19e_darwin_arm64.tar.gz | 3.4M | 3039239c3f20054c… |
| Linux · x86_64 · tar.gz hunto_351b19e_linux_amd64.tar.gz | 3.6M | 1bbf93db8441860a… |
| Linux · arm64 · tar.gz hunto_351b19e_linux_arm64.tar.gz | 3.2M | 0b7c93f8ae95becc… |
| Windows · x86_64 · hunto.exe hunto_351b19e_windows_amd64.exe | 8.9M | 6b0a5bab7e1b85c5… |
| Windows · x86_64 · zip hunto_351b19e_windows_amd64.zip | 3.7M | 00d4a201eecf0366… |
| Windows · arm64 · zip hunto_351b19e_windows_arm64.zip | 3.3M | 9291bf19e7d21c04… |
Full checksums: checksums.txt
curl -fsSLO http://cli-ef9097.pages.tik.co/download/hunto_0.0.0+351b19e-1_amd64.deb
sudo dpkg -i hunto_0.0.0+351b19e-1_amd64.deb
hunto version
# Apple Silicon; use darwin_amd64 on Intel
curl -fsSL http://cli-ef9097.pages.tik.co/download/hunto_351b19e_darwin_arm64.tar.gz | tar xz
sudo install hunto_darwin_arm64/hunto /usr/local/bin/hunto
hunto version
The binary is unsigned, so Gatekeeper will quarantine it on first run.
Clear it with xattr -d com.apple.quarantine /usr/local/bin/hunto, or ship a
signed build once an Apple Developer ID is available.
curl.exe -fsSLO http://cli-ef9097.pages.tik.co/download/hunto_351b19e_windows_amd64.exe
.\hunto_351b19e_windows_amd64.exe version
Unsigned, so SmartScreen will warn on first run. The .zip
above contains the same binary named hunto.exe alongside the docs.
curl -fsSL http://cli-ef9097.pages.tik.co/download/hunto_351b19e_linux_amd64.tar.gz | tar xz
sudo install hunto_linux_amd64/hunto /usr/local/bin/hunto
hunto profile set dev --server https://hunto.example --activate
hunto auth login # credential read from stdin, stored 0600
hunto modules # what this build can reach
hunto capabilities --check # does every capability still bind on that server?
hunto mcp serve runs a Model Context Protocol server over stdio. It offers the same
commands as the CLI, through the same profile and credential.
# Claude Code
claude mcp add hunto -- hunto mcp serve
# Claude Desktop, Cursor and other clients that read an mcpServers block
{ "mcpServers": { "hunto": { "command": "hunto", "args": ["mcp", "serve"],
"env": { "HUNTO_SERVER": "https://in.hunto.ai", "HUNTO_TOKEN": "hnt_…" } } } }
By default an agent is offered read commands only. There is no per-call confirmation over MCP, so a flag on the server is the confirmation:
| Flag | Also offers |
|---|---|
--allow-costly | Commands that spend provider credits or model time: start a run, create a schedule, test a flow. |
--allow-write | Commands that change data: update or delete a flow, cancel a run. |
The flags are independent. Tools are named module_group_verb, for example
monitor_assets_list. A result over 100 KB is cut and the cut is announced. The agent acts as the
owner of the credential, so use an API key for an account that can see only what the agent should.
On Windows use hunto.exe as the command.
No install? The Hunto web server also hosts an MCP endpoint, with sign-in or API-key access:
https://in.hunto.ai/api/mcp (India) and https://eu.hunto.ai/api/mcp (EU). It is described in the
Hunto knowledge base as “Connect an AI assistant to Hunto (MCP)”.
Built from 351b19e3cae44fd0a6548928c086466bfad2d6fc · source.
Verify a download: sha256sum -c checksums.txt --ignore-missing.