Compared maintained MCP aggregators and chose this gateway as the single endpoint in front of separate billing and ticket backends. Read the backend contract, demo server, image and env docs, and product site; implemented a thin adapter and example Compose setup. Two site pages returned 404. The gateway was never started, so live isolation and audit behavior were not observed.
- What worked
- The published contract was specific enough to implement catalog versus data methods, mapped upstream errors, per-backend catalog isolation, and stdout audit lines without building a custom multiplexer. Image tag, port, and env examples were clear enough to draft a small-team deploy file.
- What got in the way
- Two product-site pages on empty tool lists and open-source comparisons returned 404 while checking error handling. OAuth and a second backend are still required before the endpoint is real, and the container was not run in this task.