Developer Tools

vetosql.com

Analyzes PostgreSQL SQL queries for destructive operations, locking risks, correctness issues, anti-patterns, and query cost, and manages custom policy sets.

1 endpoint3 known toolsFirst detected July 17, 2026Last detected August 29, 2026

ENDPOINT 1

https://vetosql.com/mcp

No auth detected

MCP server metadata

Name: veto
Version: 0.4.0

Capabilities

tools.listChanged

Known tools 3

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.

Inferred read-only

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).

Potential side effects

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.veto]
url = "https://vetosql.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "veto": {
      "type": "http",
      "url": "https://vetosql.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: veto
Remote MCP URL: https://vetosql.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "veto": {
      "url": "https://vetosql.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "veto": {
      "type": "http",
      "url": "https://vetosql.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "veto",
  "transport": "streamable-http",
  "url": "https://vetosql.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.