I feel most of the comments here are from bots
To be fair, it is really simple to build your own proxy. I built a custom authentication layer with logging and limits for Dify MCP with just 2 prompts in Kimi.
Later built it out with database limts etc.
This is awesome. Your comparison make it easy. This approach makes perfect sense to give 100% visibility into the back and forth.<p>Is it possible to add a simple browser page to brows the data in a simple way?. Thank you.
Great. I dream to see MCP of MCP, discovery, installation, security and usage should be automatic.
Its really a great tool. The gap of visualization of calling the AI client is covered by your product!!
This is awesome, thank you. What's missing now is an MCP for Wireshark.
Thanks! Actually, there is already an MCP for Wireshark, for example <a href="https://github.com/0xKoda/WireMCP" rel="nofollow">https://github.com/0xKoda/WireMCP</a>
Remote debugging and post-mortem debugging support might be useful.<p>There are many AI auditability proxies;<p>awesome-auditable-ai: "A curated list of papers, tools, datasets, benchmarks, and standards for building, evaluating, and auditing reliable AI agents" <a href="https://github.com/yzhao062/awesome-auditable-ai" rel="nofollow">https://github.com/yzhao062/awesome-auditable-ai</a><p>Aegis and LiteLLM, for example, are pre-execution firewalls that add a cryptographic audit trail. <a href="https://github.com/Justin0504/aegis" rel="nofollow">https://github.com/Justin0504/aegis</a>
[flagged]
[flagged]