Anyone else noticed AI search is actually sending traffic now?

I've been obsessing over this for a while now.

Google traffic has dropped on a few sites I work on, nothing crazy but definitely noticeable but weirdly I'm starting to see visits coming from Perplexity and ChatGPT in my analytics.

The thing is I have no idea if my brand is actually being mentioned or recommended by these tools or if I'm just getting lucky. There's nothing in Search Console that tells you this.

Anyone actually tracking this properly? Feel like I'm flying blind and GEO is just becoming too important to ignore now.

reddit.com
u/LeatherHot940 — 6 days ago
▲ 1 r/mcp

Does anyone else have no idea what their MCP servers are actually doing at runtime?

Once I’ve got a few wired into Claude Desktop / Cursor, I lose all visibility and I’m not sure which tool got called, what came back, why something silently failed. The agent does something and I’m guessing.

Is this a real problem for anyone else, or is there an obvious tool I’m missing? How are you all handling it, by actually watching the calls, or just digging through logs when something breaks?

reddit.com
u/LeatherHot940 — 30 days ago
▲ 1 r/mcp

Built a MCP proxy in Go after spending way too long debugging a silent tool failure

Been building with MCP servers for the past few months and kept hitting the same wall where Claude says something went wrong, and you I have no idea what actually happened.

The problem is you can't add debug logging to an MCP server. Built Penstock to fix this. It's a transparent proxy that sits between your MCP client and your servers. Single Go binary, no runtime dependencies.

How are you currently debugging MCP tools that have failed?

u/LeatherHot940 — 1 month ago
▲ 16 r/mcp

How are you handling auth and security on MCP servers in production?

I’ve been building agents with MCP and ran into the auth problem where there is no easy way to scope which tools an agent can call, no audit trail of what actually ran and no protection if a tool returns something malicious.

Curious how others are solving this. Are you rolling your own proxy? Just accepting the risk for now? Or is this not a problem yet because you’re still in prototyping?

Genuinely trying to understand if this is a “everyone’s hitting this” problem or a “just me” problem.

reddit.com
u/LeatherHot940 — 2 months ago

Genuinely lost count of how many hours I've spent staring at logs trying to figure out why an agent did something completely wrong.

The problem is that by the time you notice something went wrong, the context is gone. You know the output was bad but you have no idea what the agents were actually doing — which handoff failed, which decision was wrong, whether it was a prompt issue or a tool issue or just the agents going in circles.

I got fed up and built something to fix it. It's called Rifft. It traces every agent decision, handoff and tool call in real time. When something breaks you can step through exactly what happened, replay the failed run, try a fix, and compare it to a run that worked.

It's free to try — rifft.dev

Would love to hear if anyone else has hit this. Curious what debugging looks like for other people building multi-agent stuff.

reddit.com
u/LeatherHot940 — 2 months ago