External endpointresponds
MCP-native URL security scanner that protects AI agent workflows.
Analyzes threats and verifies URLs align with the agent's intended goal.
Endpoint URL
https://urlcheck.ai/mcpCurrent status
responds
Last checked
Aug 17, 2026, 05:08 AM UTC
Check
MCP initialize · 8s limit
Latency
256 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
ai.urlcheck/urlcheck-mcp
Current observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- ai.preclick/preclick-mcp
- Version
- 0.3.6
- Capability keys
- tools, tasks
- Tool names
- url_scanner_async_scan, url_scanner_async_scan_with_intent, url_scanner_async_task_result, url_scanner_async_task_status, url_scanner_scan, url_scanner_scan_with_intent
Instructions excerpt
Use url_scanner_scan or url_scanner_scan_with_intent to analyze URLs for security threats. The scan runs asynchronously - use task parameter and poll tasks/get or tasks/result for results. Typical full scan duration: around 70-80 seconds. If your client does not support the MCP Tasks protocol, use the async compatibility tools instead: url_scanner_async_scan (or url_scanner_async_scan_with_intent) to submit, then url_scanner_async_task_status or url_scanner_async_task_result to poll.
Reported Aug 17, 2026, 05:08 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 175ms
- respondsMCP initialize · 8s limit · HTTP 200 · 269ms
- respondsMCP initialize · 8s limit · HTTP 200 · 290ms
- respondsMCP initialize · 8s limit · HTTP 200 · 256ms