Veto — SQL Safety & Cost Oracle is answering right now. Last checked 5 min ago. It exposes 3 tools. Last commit 14 Jun 2026.
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
Today is the operative word: we check Veto — SQL Safety & Cost Oracle every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
claude mcp add veto --transport http https://vetosql.com/mcp
https://vetosql.com/mcp
[mcp_servers.veto]
url = "https://vetosql.com/mcp"
{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}
{
"servers": {
"veto": {
"type": "http",
"url": "https://vetosql.com/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_policies
set_policies
analyze_sql
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://vetosql.com/mcp | streamable-http | answering | 215 ms | 5 min ago |
Deterministic SQL compiler for AI agents. Your agent stops guessing SQL.
Database guardrails for AI agents: check SQL against your Vericto rules before it runs.
Governed, read-only Postgres access for AI agents: SQL safety, RLS, budgets, tamper-evident audit.
Check SQL against your Vericto rules before it runs: blocks destructive or risky statements.
Read-only PostgreSQL for AI agents: every statement is checked before it runs. No account needed.
112 rules that catch dangerous PostgreSQL migrations, plus a pass/fail gate to call before any DDL.
RLS/tenant-aware Postgres for AI agents — schema, read-only SQL, NL→SQL with safety rails.
Local-first memory for AI agents: SQLite FTS5, deterministic recall, no vector DB, no cloud.
Answers built from our own checks of this server.