MCP.Market

Veto — SQL Safety & Cost Oracle MCP server

online · 100% uptime
by vetosql.com·com.vetosql/veto·v0.5.0
No reviews yet

Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.

B80/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Veto — SQL Safety & Cost Oracle yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Veto — SQL Safety & Cost Oracle tools (3)

write = sends, deletes, buys or posts
  • analyze_sqlFree

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

  • get_policiesFree

    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_policiesFree

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

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 630ms20/20
  • Tool poisoning3 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 103 days ago8/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Veto — SQL Safety & Cost Oracle compares

Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 50% of 802 Databases servers
Tools
3
the typical Databases server has 8
Tools that change things
0%
typical: 10%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote Databases server answers 100%
Response time
136 ms
faster than 76% of 292 Databases servers

What its tools let an agent do: 2 read · 1 change

Install Veto — SQL Safety & Cost Oracle in Claude Code, Cursor or VS Code

claude mcp add --transport http veto https://vetosql.com/mcp
Add to Cursor

What the publisher says

From the Veto — SQL Safety & Cost Oracle repository's README, as published. We do not edit it. Read it on GitHub

Veto — SQL Safety & Cost Oracle (MCP)

Veto is a deterministic MCP server that vets Postgres SQL for safety, correctness, and cost before an AI coding agent runs it. It returns an ok / warn / block verdict on every statement — no LLM in the core, and it never connects to your database.

Website: https://vetosql.com · MCP endpoint: https://vetosql.com/mcp (remote, streamable-http)

AI coding agents (Claude Code, Cursor, …) write and execute SQL. Occasionally they write DELETE FROM payments with no WHERE, or a DROP TABLE during a migration. More prompting doesn't fix a probabilistic system — a deterministic gate does. Veto is that gate: given the same statement, it returns the same verdict, every time, with stable finding ids you can audit and gate CI on.

What it catches

Every finding carries a stable dotted id (e.g. destructive.deletewithoutwhere) so your pipeline can branch on it. The exact rule set lives server-side and evolves over time.

Why deterministic

  • Reproducible — same input, same verdict. Testable, so trustable.
  • Auditable — a named rule fired, not "the model felt it was risky."
  • No drift — can't be talked out of a block by a clever prompt; doesn't get worse on a bad day.
  • Never touches your DB — cost is measured with a real EXPLAIN on a throwaway scratch Postgres inside a transaction that is always rolled back. Your production database is never connected.

Tools

analyze_sql

Returns a deterministic safety + cost verdict for Postgres SQL / migrations.

Returns { verdict, findings[], plan?, meta } where verdict ∈ ok | warn | block.

setpolicies (Pro)*

Stores custom org policies keyed to your Pro key; analyzesql then enforces them on top of the built-in rules. Policies are declarative data — validated and never executed** (max 50, replaces the previously stored set).

Each policy: table (exact name or glob, e.g. payments, audit, ), operations (any of select/insert/update/delete/truncate/drop/alter), action (block/warn), optional message.

{
  "policies": [
    { "table": "payments", "operations": ["delete", "truncate"], "action": "block",
      "message": "Never delete from payments — use the refund flow." }
  ]
}

Sending the full set updates it; sending an empty array clears it.

getpolicies (Pro)*

Returns the custom org policy set currently stored for your key — the same rules analyze_sql enforces on top of the built-ins. Read-only; returns an empty list if none are set.

Setup

Veto is a remote MCP server — no install, no source needed. Point your client at the endpoint.

Claude Code — .mcp.json

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

Cursor — ~/.cursor/mcp.json

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Veto — SQL Safety & Cost Oracle: common questions

Is Veto — SQL Safety & Cost Oracle MCP server safe?
Mostly: it is graded B (80/100). Read the Veto — SQL Safety & Cost Oracle safety report
How do I install Veto — SQL Safety & Cost Oracle?
It runs remotely at vetosql.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Veto — SQL Safety & Cost Oracle need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Veto — SQL Safety & Cost Oracle maintained?
The last commit was 141 days ago (2026-06-16). The latest release is v0.5.0.
Is Veto — SQL Safety & Cost Oracle up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Veto — SQL Safety & Cost Oracle?
Servers from other publishers that do the same job: DBHub MCP server, Faucet MCP server and Viberaven MCP server.
How does Veto — SQL Safety & Cost Oracle compare with other Databases MCP servers?
safety score 80/100 (higher than 50% of 802 Databases servers); tools 3 (the typical Databases server has 8); tools that change things 0% (typical: 10%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Veto — SQL Safety & Cost Oracle

Same job from other publishers: the closest match first, then the best rated.

  • DBHub
    Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
    A
  • Faucet
    SQL database to MCP tools and REST API: PostgreSQL, MySQL, SQL Server, Oracle, SQLite, Snowflake.
    A
  • Viberaven
    Checks a Vercel + Supabase repo before deploy: RLS, grants, leaked keys, webhooks. Runs locally.
    A
  • Sqlsure
    Semantic SQL inspector: catches double-counting, wrong joins, PII exposure before execution.
    A
  • Quarry
    Safety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default.
    A