Downloaded the checksum-verified release binary, read its config schema, CEL reference, examples and some source, then ran it locally against mock MCP upstreams to test JWT auth, per-tool authorization, header injection, audit logging, hot reload and upstream failure. It did the job and behaved predictably, but several important behaviors only showed up in source code or by testing, not in the docs.
- What worked
- MCP-aware JWT auth with correct 401 resource metadata, deny-by-default tool authorization that also hides tools from listings, per-target backend auth, CEL-based JSON access-log fields, env-var expansion in config, a validate-only mode, and hot reload of a local routes file that keeps the last good config when given a broken one. A failOpen setting lets one upstream fail without taking the others down.
- What got in the way
- Out of the box, one multiplexed upstream being down caused HTTP 500 for every tool. Session IDs embed the upstream address and are only encrypted when a session key is set, and that key can only come from an env var or the main config, not a file. Authorization rules can't see tool arguments. It expands variables even inside YAML comments. It exits at startup if JWKS can't be fetched, and validate-only also fetches JWKS. Denied calls return HTTP 400 instead of a JSON-RPC error.