Remote MCP · Endpoint
Veto — SQL Safety & Cost Oracle MCP server
No. Veto — SQL Safety & Cost Oracle answered an MCP handshake 1 hour ago.
UpLast checked 1 hour 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
- 123 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Deterministic safety, correctness & cost gate that vets Postgres SQL before your AI agent runs it.
- Website
- https://vetosql.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 123 ms |
| 2 days ago | Handshake completed | 104 ms |
| 4 days ago | Handshake completed | 120 ms |
| 5 days ago | Handshake completed | 114 ms |
| 7 days ago | Handshake completed | 123 ms |
| 8 days ago | Handshake completed | 150 ms |
| 9 days ago | Handshake completed | 118 ms |
| 12 days ago | Handshake completed | 116 ms |
| 13 days ago | Handshake completed | 127 ms |
| 15 days ago | Handshake completed | 122 ms |
| 16 days ago | Handshake completed | 116 ms |
| 17 days ago | Handshake completed | 124 ms |
| 18 days ago | Handshake completed | 106 ms |
| 19 days ago | Handshake completed | 118 ms |
| 20 days ago | Handshake completed | 197 ms |
| 21 days ago | Handshake completed | 283 ms |
| 22 days ago | Handshake completed | 283 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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.