xyzDB

Language

The agent talks to its data directly.

The MCP server lives inside the binary itself: no bridge, no sidecar to deploy — the agent's own process opens the data. And a policy classifies every query by its structure before it reaches the engine, so you can hold an agent to read-only or no-deletes and it can't slip past — not even with a malformed query. It reads whatever it needs; it deletes only if you allow it.

agentMCP client--embed · in-process--connect · TCPxyzDB · single binaryMCP server4 tools · 3 resources · read-only policyturba enginegravity · ghosts · vectorsnative from origin — no bridge, no sidecar
Language·4/6