Connect Vericto to your stack in minutes.
TCP proxy, Runtime API, CLI, Validation API, or MCP for AI agents. Vericto works with any driver, ORM or pipeline that uses a standard connection string, without rewriting your code.
DATABASE_URL=postgres://vericto-proxy:5433/db
curl .../api/v1/proxy/query -d '{"query":"DELETE FROM users"}'
curl .../api/v1/ci/check-key -d '{"sql":"DELETE FROM users"}'
vericto check migrations/0001.sql
check_sql {"sql": "DELETE FROM users"}
Connection modes
Pick the one that fits your architecture. The same deterministic AST evaluation across all five.
TCP proxy
The simplest way: point your connection string at the Vericto proxy instead of your database. It intercepts every query at the protocol level (Postgres/MySQL) and blocks destructive ones before they land. Zero code changes.
Runtime API
Runtime protection from your code: your application sends each query to /api/v1/proxy/query, one per call, and runs it only if it is not blocked. The verdict is enforced as far as your application honours it. It is recorded in Queries, like with the TCP proxy. All four dialects.
CLI
The vericto binary validates SQL against your workspace rules in pre-commit hooks and CI/CD pipelines. Exit code mirrors the verdict. Binaries for Linux, macOS and Windows published on every release.
Validation API
Checks batches of SQL without running them, from your own tools: /api/v1/ci/check-key returns a verdict per statement and an exit_code. Nothing is executed. All four dialects.
MCP
Your coding agent (Claude Code or another MCP client) checks SQL against your workspace rules while it writes it, before the commit. A remote MCP server: paste a URL and your API key, nothing to install.
Which mode should you use?
| TCP proxy | Runtime API | CLI | Validation API | MCP | |
|---|---|---|---|---|---|
| Zero code changes | ✓ | — | — | — | — |
| Inline blocking (in the query path) | ✓ | — | — | — | — |
| Runtime protection (the query runs only if it is not blocked) | ✓ | If your app honours the verdict | — | — | — |
| Checks SQL without running it | — | — | ✓ | ✓ | ✓ |
| Ideal for CI/CD and pre-commit | — | — | ✓ | ✓ | — |
| Requires deploying the proxy | ✓ | — | — | — | — |
| Dialects | Postgres · MySQL | All 4 | All 4 | All 4 | All 4 |
| Checks SQL while the agent writes it | — | — | — | — | ✓ |
Databases
PostgreSQL
Full Postgres dialect support (CTEs, subqueries, extensions) using pg_query, the official parser. Available via inline TCP proxy or the HTTP evaluation API.
TCP ProtocolVia APICLI
MySQL
Full MySQL dialect support with dialect-specific semantic rules: DELETE with LIMIT is valid in MySQL, Vericto applies the correct rules. Available via inline TCP proxy or the HTTP API.
TCP ProtocolVia APICLI
Oracle
Oracle dialect support via the HTTP evaluation API (no TCP wire proxy for Oracle yet). Blocks DELETE/UPDATE without WHERE, DROP TABLE, and TRUNCATE with the same deterministic AST parser.
Via APICLI
SQL Server
MSSQL / SQL Server dialect support via the HTTP evaluation API (no TCP wire proxy yet). AST parsing with T-SQL semantic rules, including CTEs and proprietary syntax.
Via APICLI
SQLite
Roadmap: SQLite dialect support for agents and embedded environments. Ideal for protecting AI pipelines in edge functions and CLI tools with local database access.
COMING SOON
Snowflake
Roadmap: protection for LLM analytics pipelines on Snowflake. Will block TRUNCATE and DROP on production data warehouses.
COMING SOONFrameworks & tools
LangChain
Compatible with any LangChain agent that uses SQLDatabase. Just change the connection string in your SQLAlchemy engine.
Compatible
Vercel AI SDK
Vericto is transparent to Text-to-SQL pipelines built with the Vercel AI SDK: because the proxy intercepts at the database wire protocol, it protects generated queries no matter how they were produced. No changes to your generation code.
Compatible
Supabase
Protect your Supabase database from destructive agent queries. Being Postgres, it works with the native TCP proxy: point your connection string at the proxy, no code changes.
Compatible
MCP Servers
Vericto's remote MCP server: Claude Code, Kiro and other MCP clients call check_sql and get your rules' verdict before they run the SQL.
Native
GitHub Actions
Native GitHub Actions integration for dry-run in CI/CD. Inline PR annotations flagging destructive queries with the rule code and fix suggestion.
CI/CDGitLab CI
Run the Vericto CLI as a job in your GitLab CI pipeline. Validate SQL changes on every merge request and stop the pipeline if a destructive query appears.
CI/CDReady to connect your stack?
Get started free with the TCP proxy in minutes, or check the integration guide for the step-by-step detail.