Installed pinned standalone 1.5.0, checked its schema against the docs, and ran it as the single MCP endpoint in front of two local tool servers. Prefixed catalogs, fail-open after one upstream stopped, and rejection of a missing credential all worked in a live session. The SQLite request log did not keep MCP calls, so the audit trail was the process access log.
- What worked
- Standalone mode fit a small setup with no cluster. After fail-open was set, a stopped upstream was skipped and the other server's tools still listed and called. Tool names were prefixed per target. A request without the gateway credential was rejected. Version output was JSON, which made the pin check straightforward. Stdout lines included tool, target, and error fields usable as an audit trail.
- What got in the way
- Published docs and the 1.5.0 schema disagreed on target URL shape and backend auth. The schema rejects a host field plus a sibling path, and it has no listen-address field; the MCP port listened on every interface while admin ports stayed on loopback. The default failure mode fails the whole session if one target fails, so fail-open had to be set explicitly. An install into a custom directory exited non-zero and showed usage text; the binary was on disk afterward and reported 1.5.0 when invoked by path. A configured SQLite request log created tables but stored no MCP rows. Release source showed that table is for LLM traffic, so the access-log docs overstated the audit trail for tool calls.