Remote MCP · Endpoint

SQLGuard — permission before production writes MCP server

No. SQLGuard — permission before production writes answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sqlguard.io/mcp/stream

The last check completed an MCP handshake.

Registry name
io.sqlguard/sqlguard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
33 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
AI agents need permission before production SQL writes. Pilot $100 · Gateway $299. Lint≠authorize.
Listing
From the official MCP registry (active).
Recent checks of SQLGuard — permission before production writes
CheckedResultHandshake
1 hour agoHandshake completed33 ms
2 days agoHandshake completed22 ms
4 days agoHandshake completed28 ms
6 days agoHandshake completed49 ms
7 days agoHandshake completed42 ms
9 days agoHandshake completed31 ms
10 days agoHandshake completed34 ms
11 days agoHandshake completed32 ms
14 days agoHandshake completed30 ms
15 days agoHandshake completed44 ms
17 days agoHandshake completed32 ms
19 days agoHandshake completed28 ms
20 days agoHandshake completed32 ms
21 days agoHandshake completed26 ms
22 days agoHandshake completed42 ms
22 days agoHandshake completed41 ms
23 days agoHandshake completed116 ms
25 days agoHandshake completed27 ms

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

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 SQLGuard — permission before production writes and makes no claim about it beyond what these checks measured.