Menu

1 / 4

Lost updates in four MCP servers: GitHub, Grafana, PostHog and Kubernetes

DEV Community: go·Joshua Bryan·4 days ago
#CVLof8l1
#devtogo#devto#dev#server#grafana
Reading 0:00
15s threshold

Two agents changed different fields of the same GitHub issue at the same moment, through GitHub's official MCP server. Both were told the write succeeded. In 19 of 30 pairs, one of the two changes was gone. GitHub's own per-field API, given the same two changes, lost none in 28.

I run IsoKron, which sells MCP audits. This is self-funded research, AI-assisted, and not commissioned or endorsed by GitHub, Grafana Labs, PostHog, the kubernetes-mcp-server maintainers or Red Hat. It was first published on isokron.ai .

We audited the MCP servers that GitHub, Grafana and PostHog publish for their own products, and the open-source containers/kubernetes-mcp-server . In the first three, two writes sent at the same moment to the same object could lose one of the changes, and both callers were told their write had succeeded. In the Kubernetes server, a full copy of an object re-applied through the tool without its resourceVersion , after another writer had changed a field, set that field back.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.