Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
1–10 of 29 posts
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#2[flagged]
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#3This is awesome, thank you. What's missing now is an MCP for Wireshark.
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#4This is awesome, thank you. What's missing now is an MCP for Wireshark.
Thanks! Actually, there is already an MCP for Wireshark, for example https://github.com/0xKoda/WireMCP
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#5Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#6This is awesome. Your comparison make it easy. This approach makes perfect sense to give 100% visibility into the back and forth.
Is it possible to add a simple browser page to brows the data in a simple way?. Thank you.
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#7Its really a great tool. The gap of visualization of calling the AI client is covered by your product!!
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#8This is awesome. Your comparison make it easy. This approach makes perfect sense to give 100% visibility into the back and forth. Is it possible to add a simple browser page to brows the data in a simple way?. Thank you.
Thank you! Showing the data in a web page should definitely be possible. But I’m not sure if this matches the original idea I had, where the tool would run in the terminal only. Why do you feel the need to show the data in a web page? Is there anything missing in the CLI?
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#9Its really a great tool. The gap of visualization of calling the AI client is covered by your product!!
Thanks a lot!
Re: Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)
#10To 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.