The administration world of the MCP server is where an operator's assistant earns trust or loses it. This release fills it with tools that plan before they act, prove what they did, and answer the questions an administrator asks most.
Provisioning
- Plan, apply, verify Creating a database or an engine user, and granting, revoking or dropping one, runs through the driver interface in three steps, dry-run by default, every command journalled with the password redacted. Proven on Informix, PostgreSQL, MySQL, SQL Server and Oracle. There is no drop-database tool, by contract.
- A leak closed on the way Tool arguments had been persisted verbatim in the call log. Secret-named arguments are now masked at any depth.
Checks
- Server, database, user, Redis A pool-independent server probe, a six-step database health chain, a user check and a Redis check, plus a ping whose checkout runs the initial SQL, so it counts as a served request.
Users and security
- Nine lifecycle tools Block with a required reason, reset a password returned once, reset the second factor, revoke tokens through a new signing salt, kill a session.
- Security in one answer A user's effective security replaces six calls and a join in the reader's head; a table's row security dry-runs the injector; a user's refused verbs are named to the layer that refuses them, from the physical grant to the transaction item.
- Conditions proven first A role write proves its SQL condition against a data database before storing it.
Sixty prompts accompanied the tools at that point, each a procedure an administrator used to carry in their head.