Skip to content
LiciumTalk to usFor agentsSign in

MCP server list / MCP-native URL security scanner that protects AI agent workflows.

Analyzes threats and verifies URLs align with the agent's intended goal.

Answered:

4 of 4 checks

Status
responds
Typical response time
262.5 ms
Last checked
Latest check:
This server answered at its latest check.Last checked  · MCP initialize · 8s limit · HTTP 200 · answered in 256 ms.
Address
https://urlcheck.ai/mcp
Listed in:
official MCP registry mcp_registry
Registry name
ai.urlcheck/urlcheck-mcp
Transport
streamable HTTP streamable-http
Host
urlcheck.ai

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

What the server says about itself

We have not checked it.
Server name:
ai.preclick/preclick-mcp
Version:
0.3.6
MCP features it lists:
tools, tasks
Tool names:
url_scanner_async_scanurl_scanner_async_scan_with_intenturl_scanner_async_task_resulturl_scanner_async_task_statusurl_scanner_scanurl_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_sc…

Reported Aug 17, 2026, 05:08 AM UTC.

Check history

oldest to newest; each row is one recorded check
Recorded checks for MCP-native URL security scanner that protects AI agent workflows.
CheckedStatusTookCheck
responds175 msMCP initialize · 8s limit · HTTP 200
responds269 msMCP initialize · 8s limit · HTTP 200
responds290 msMCP initialize · 8s limit · HTTP 200
responds256 msMCP initialize · 8s limit · HTTP 200

Need a different server, page or part?

Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.