Remote MCP · Endpoint
PreClick — An MCP-native URL preflight scanning service for autonomous agents (formerly URLCheck). MCP server
No. PreClick — An MCP-native URL preflight scanning service for autonomous agents (formerly URLCheck). answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://urlcheck.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.urlcheck/urlcheck-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 173 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- PreClick scans links for threats and confirms intent match with high accuracy before agents click.
- Website
- https://preclick.ai/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 173 ms |
| 10 hours ago | Handshake completed | 321 ms |
| 1 day ago | Handshake completed | 176 ms |
| 2 days ago | Handshake completed | 136 ms |
| 4 days ago | Handshake completed | 148 ms |
| 4 days ago | Handshake completed | 148 ms |
| 5 days ago | Handshake completed | 305 ms |
| 6 days ago | Handshake completed | 143 ms |
| 8 days ago | Handshake completed | 369 ms |
| 11 days ago | Handshake completed | 255 ms |
| 13 days ago | Handshake completed | 167 ms |
| 16 days ago | Handshake completed | 135 ms |
| 18 days ago | Handshake completed | 206 ms |
| 20 days ago | Handshake completed | 155 ms |
| 22 days ago | Handshake completed | 133 ms |
| 24 days ago | Handshake completed | 152 ms |
| 26 days ago | Handshake completed | 119 ms |
| 27 days ago | Handshake completed | 139 ms |
| 29 days ago | Handshake completed | 145 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 PreClick — An MCP-native URL preflight scanning service for autonomous agents (formerly URLCheck). and makes no claim about it beyond what these checks measured.