Veto — SQL Safety & Cost Oracle
com.vetosql/vetoVersion 0.5.0Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
Status
Responds92 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:21 UTC
- Latency
- 92 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://vetosql.com/mcpResponds92 msNo sign-in
Claude Code
claude mcp add --transport http veto https://vetosql.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: veto
Remote MCP server URL: https://vetosql.com/mcpCursor
{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"veto","type":"http","url":"https://vetosql.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
analyze_sqlAnalyze Postgres SQL/migrations for destructive operations, locking risk, correctness traps (NULL handling that silently returns wrong results), anti-patterns, and query cost. Returns a deterministic verdict (ok/warn/block) with findings. Pass the optional `schema` argument (your CREATE TABLE/INDEX DDL) to also get EXPLAIN-based cost analysis run on a throwaway scratch Postgres — no separate tool or DB connection needed. | Not declared | Not declared | Not declared | Not declared |
get_policiesReturn the custom org policy set currently stored for your Pro key — the same rules analyze_sql enforces on top of the built-ins. Read-only; returns an empty list if none are set. Use set_policies to change them. | Not declared | Not declared | Not declared | Not declared |
set_policiesReplace the stored custom org policy set for your Pro key (this is also how you update or clear them: send the full new set to update, or an empty array to remove all). Each policy blocks or warns on an operation against matching tables (e.g. no DELETE on payments). Policies are declarative data — validated, never executed — and apply transparently to every later analyze_sql call made with this key. Use get_policies to read the current set. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Jun 14, 2026
- Updated
- Jun 14, 2026
- Categories (suggested)
- DatabasesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared