veto is a remote MCP server that gives an AI agent 3 tools, among them analyze_sql, get_policies, set_policies. It answers at https://vetosql.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
analyze_sql | Analyze 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. P Inputs: sql, schema, rowCountHints, dialect |
get_policies | Return 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. |
set_policies | Replace 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. Inputs: policies |
Every block below points at https://vetosql.com/mcp. Pick your client and copy.
claude mcp add --transport http veto https://vetosql.com/mcp
{
"mcpServers": {
"veto": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vetosql.com/mcp"]
}
}
}{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}{
"servers": {
"veto": {
"type": "http",
"url": "https://vetosql.com/mcp"
}
}
}{
"context_servers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}{
"mcpServers": {
"veto": {
"serverUrl": "https://vetosql.com/mcp"
}
}
}{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}name: veto
version: 0.0.1
schema: v1
mcpServers:
- name: veto
type: streamable-http
url: https://vetosql.com/mcp{
"mcpServers": {
"veto": {
"httpUrl": "https://vetosql.com/mcp"
}
}
}{
"mcpServers": {
"veto": {
"type": "http",
"url": "https://vetosql.com/mcp"
}
}
}{
"mcpServers": {
"veto": {
"url": "https://vetosql.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fvetosql.com%2Fmcp&type=streamable_http&id=veto&name=veto
It answered our last check on 18 October 2026 in 107 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vetosql.com and served from vetosql.com, the vendor's own domain: https://vetosql.com/mcp.
3, as returned by the server's own tools/list on 31 August 2026: analyze_sql, get_policies, set_policies.
It answered our last check on 18 October 2026 in 107 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vetosql.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.vetosql. Endpoint host: vetosql.com. ARD identifier: urn:air:com.vetosql:mcp:veto.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.