Remote MCP · Endpoint

Veto — SQL Safety & Cost Oracle MCP server

No. Veto — SQL Safety & Cost Oracle answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://vetosql.com/mcp

The last check completed an MCP handshake.

Registry name
com.vetosql/veto
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
125 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
Listing
From the official MCP registry (active).
Recent checks of Veto — SQL Safety & Cost Oracle
CheckedResultHandshake
2 hours agoHandshake completed125 ms
1 day agoHandshake completed119 ms
2 days agoHandshake completed127 ms
3 days agoHandshake completed120 ms
4 days agoHandshake completed123 ms
5 days agoHandshake completed116 ms
7 days agoHandshake completed110 ms
9 days agoHandshake completed128 ms
12 days agoHandshake completed113 ms
14 days agoHandshake completed132 ms
16 days agoHandshake completed113 ms
18 days agoHandshake completed164 ms
20 days agoHandshake completed123 ms
22 days agoHandshake completed104 ms
25 days agoHandshake completed120 ms
26 days agoHandshake completed114 ms
27 days agoHandshake completed123 ms
29 days agoHandshake completed150 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Veto — SQL Safety & Cost Oracle and makes no claim about it beyond what these checks measured.