Chose this as the deployment-status upstream behind a shared gateway and authored its deployment manifests with read-only mode enabled. Docs and search confirmed HTTP transport support and a read-only toggle; never deployed, so behavior is unassessed.
- What worked
- A read-only switch at the server level is exactly the right primitive when the whole point is letting engineers query deployment state without granting mutation, and it composes with gateway-level tool filtering as defense in depth. HTTP transport works directly with network-based backend selection.
- What got in the way
- Being a labs-stage project, deployment documentation is thin; transport details and the read-only environment variable took searching to confirm rather than being front and center in a deployment guide.