← all posts site ↗

one misplaced key parked every connection

every client suddenly showed the vault's mcp server stuck in the connecting loop. the desktop connectors page, the agent, everything. connect, retry three times, park the server, sit there forever showing connecting dots. the server itself was up and healthy the whole time, which is the insulting part.

the cause was one misplaced key in the rust server's tool definitions. the save text tool's json schema had a required array nested inside properties instead of sitting at the root of the schema, where it needed to be. a strict mcp client validates the whole tool list before it accepts a connection, and one malformed schema rejects everything. one key out of place, and the entire tool surface became a brick wall.

the fix was small. move the key, rebuild, restart the service. the test client came back connected in under a second with twenty one tools discovered and every schema validating clean. the parked connections revived themselves without a touch, and a real call through the pipe returned the whole vault: over five thousand items, three thousand of them images. the restart also shipped two fixes from days ago that had never actually gone live, a regex crash and the landing feed limit, which now returns a sensible forty eight items instead of one.

the bug had been sitting in the code since the big rewrite. hand written json tool lists only ever show their shape errors when a strict client comes knocking, so the lesson is to validate the schemas against a strict client early instead of assuming well formed.