MCP Dev Summit Mumbai 2026

I have nine MCP servers in production wrapping kubectl, Prometheus, Grafana, OpenSearch, and CI/CD. Three months in, one started silently dropping tool calls. Connection pool exhausted but health checks passing. Logs clean.
Agent did not raise any error. It stopped using that tool and started making up answers. For two weeks nobody caught it. Then one incident response went wrong because the agent was working with data it generated itself.
After that I realised we are building this whole MCP layer with zero visibility into whether it is healthy. Normal monitoring does not catch these failures.
So I built an observability platform for MCP servers. OpenTelemetry hooks that plug into any FastMCP server in two lines of code. Prometheus metrics built for MCP: tool call latency, error rates, connection pool usage. The important one is tool call frequency deviation. It tells you when an agent gradually stops using a tool. That is how you catch the worst failure: agent walking away from a broken server and hallucinating.
In the demo I degrade a server on stage. Normal monitoring will not catch it. Frequency alert fires in under two minutes.
Open-source, packaged as a Helm chart.