Cloud MCPengine
engine
4 MCP tools on the Hanzo cloud door that call the engine API.
The 4 tools tools/list names for engine. Each dispatches to an operation in the engine API reference.
| Tool | Route | Arguments | Description |
|---|---|---|---|
get_v1_engine_model | GET /v1/engine/model | 1 | Model reads one model's load state — loaded, unloading, or not_found, as the engine itself reports i |
get_v1_engine_models | GET /v1/engine/models | 0 | Models lists the models the engine serves, each with its load state — the server's own model table ( |
get_v1_engine_status | GET /v1/engine/status | 0 | Status reports whether the engine deployment is reachable and which build revision it runs — an hone |
get_v1_engine_system | GET /v1/engine/system | 0 | System reads the engine host's inventory: OS, CPU, memory, every accelerator device with its VRAM an |
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?