Veto — SQL Safety & Cost Oracle is answering right now. Last checked 2 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 2 min ago.
claude mcp add veto --transport http https://vetosql.com/mcp
{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}
[mcp_servers.veto]
url = "https://vetosql.com/mcp"
{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}
{
"mcpServers": {
"veto": {
"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 | 250 ms | 2 min ago |
Deterministic SQL compiler for AI agents. Your agent stops guessing SQL.
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.
Deterministic SQL formatting across 19 dialects (postgres, mysql, snowflake, bigquery, etc.).
Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default.
Governs what AI agents do: tool calls, SQL, commands, files checked against policy before they run.
Read-only PostgreSQL, Oracle and SQL Server access for AI agents: SQL, plans, schema, index stats
Answers built from our own checks of this server.