16 comments

[ 4.2 ms ] story [ 129 ms ] thread
This is awesome, thank you. What's missing now is an MCP for Wireshark.
You can just get your agent to run tshark :)
Ha, fair. tshark in a shell works fine, the only reason to wrap it is typed output and not handing the agent a raw shell.
This 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.

Its really a great tool. The gap of visualization of calling the AI client is covered by your product!!
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.
Great. I dream to see MCP of MCP, discovery, installation, security and usage should be automatic.
I feel most of the comments here are from bots
It's getting bad. Definitely a hole that needs to be filled...
One question about http mode, you carry authorization headers. Do you redact bearer tokens before captures hit the logs?
Makes sense. Payload secrets are probably the scarier part anyway. Would a simple redact config make sense, like keys/patterns to scrub before writing traces?
"MCP Inspector [...] never sees the traffic between your client and your server." This line resonates a lot, what you're building makes sense to me! I had built something similar to track these interactions and turn them into a benchmark, I'm gonna try this out.