Rendered at 21:09:27 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
rstagi 4 hours ago [-]
"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.
kerlenton 30 minutes ago [-]
Thanks, that means a lot. Would love to hear how it goes once you try it
geraldsterling 5 hours ago [-]
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?
kerlenton 14 minutes ago [-]
[dead]
cidd 1 days ago [-]
I feel most of the comments here are from bots
geraldsterling 5 hours ago [-]
It's getting bad. Definitely a hole that needs to be filled...
kerlenton 1 days ago [-]
Maybe, but I didn't do it. Perhaps people are boosting their karma?
iamgopal 1 days ago [-]
Great. I dream to see MCP of MCP, discovery, installation, security and usage should be automatic.
mmakeev 17 hours ago [-]
One question about http mode, you carry authorization headers. Do you redact bearer tokens before captures hit the logs?
kerlenton 15 hours ago [-]
There's nothing redacted because the header isn't collected in the first place. Under http mode, the proxy intercepts the JSON-RPC messages, but not their headers, so there's no way for the log to contain the Authorization header and the bearer passes through unlogged. The contents of the messages themselves aren't redacted, which means if the secret is in the payload, it'll end up in the trace. The trace stays on your machine, and if you don't want anything to go to the disk at all, use --no-trace.
mmakeev 15 hours ago [-]
thanks! all clear
tiku 1 days ago [-]
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.
kerlenton 1 days ago [-]
[dead]
chopete3 1 days ago [-]
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.
kerlenton 1 days ago [-]
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?
atmanactive 1 days ago [-]
This is awesome, thank you. What's missing now is an MCP for Wireshark.
Its really a great tool. The gap of visualization of calling the AI client is covered by your product!!
kerlenton 1 days ago [-]
Thanks a lot!
westurner 1 days ago [-]
Remote debugging and post-mortem debugging support might be useful.
There are many AI auditability proxies;
awesome-auditable-ai: "A curated list of papers, tools, datasets, benchmarks, and standards for building, evaluating, and auditing reliable AI agents" https://github.com/yzhao062/awesome-auditable-ai
Is it possible to add a simple browser page to brows the data in a simple way?. Thank you.
There are many AI auditability proxies;
awesome-auditable-ai: "A curated list of papers, tools, datasets, benchmarks, and standards for building, evaluating, and auditing reliable AI agents" https://github.com/yzhao062/awesome-auditable-ai
Aegis and LiteLLM, for example, are pre-execution firewalls that add a cryptographic audit trail. https://github.com/Justin0504/aegis