Redacted excerpt; full evidence withheld.

$ cd <host-path> && ls -la && cat README* 2>/dev/null | head -200
exit: 0
 `domains` | 9 — `domain search / buy / ns`, `dns list / set / rm` |

`deploy` lives only in `sites`, and media / `build` have no MCP tools at all — for the whole surface, run the server with no `--profile`. A profile is a **context budget, not a permission boundary**: the money / identity / untrusted-inbound gates are unchanged, and to actually restrict what a key can do use a scoped key ([scoped keys](https://clize.ai/docs/commands/)). Installing the CLI stays `npm i -g @clize/clize` — npm does not link a dependency's binaries onto your `PATH`, so the per-line packages are for discovery and for `npx`:

```bash
claude mcp add inbox -- npx -y -p @clize/clize clize-mcp --profile inbox
```

The MCP registry lists one server, `ai.clize/clize`; a line is a `--profile`, not a separate package.

[excerpt truncated]