protogrid

Search / com.vetosql/veto

Veto — SQL Safety & Cost Oracle

R0· no sign-in

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

v0.5.0 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust89of 100
Uptime, 30 days100%
Latency p50301 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "veto": {
      "type": "http",
      "url": "https://vetosql.com/mcp"
    }
  }
}
claude mcp add --transport http veto https://vetosql.com/mcp
[mcp_servers.veto]
url = "https://vetosql.com/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "veto": {
      "type": "remote",
      "url": "https://vetosql.com/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "veto": {
      "type": "http",
      "url": "https://vetosql.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=veto&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdmV0b3NxbC5jb20vbWNwIn0%3D"
}
{
  "servers": {
    "veto": {
      "type": "http",
      "url": "https://vetosql.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "veto": {
      "httpUrl": "https://vetosql.com/mcp"
    }
  }
}
extensions:
  "veto":
    enabled: true
    name: "veto"
    type: streamable_http
    uri: "https://vetosql.com/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_policies (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); analyze_sql (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); set_policies (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 666 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 666 tokens to load them all · tool set 5314d918b58b · checked 2026-10-20 10:35 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 89 / 100

provenance85
liveness100
freshness65
hygiene100

+repository +dns-namespace +website +reachable +uptime-100% ~updated-128d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://vetosql.com/mcp streamable-httpnoneyes100%301 ms2025-11-252026-10-20

Tools (3)

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

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.vetosql/veto",
  "title": "Veto — SQL Safety & Cost Oracle",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://vetosql.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.5.0",
  "repository": {
    "url": "https://github.com/metaweardigital/veto-mcp",
    "source": "github"
  },
  "websiteUrl": "https://vetosql.com",
  "description": "Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it."
}