flagrixofficial
A
license-
qualityB
maintenanceEnables AI agents to scan GitHub repositories and user profiles for malware signals before cloning, providing risk verdicts pinned to specific commits.
Last updated
654
MIT
PreClick — An MCP-native URL preflight scanning service for autonomous agents.
by ai.preclick
Server Details
PreClick scans links for threats and confirms intent match with high accuracy before agents click.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cybrlab-ai/preclick-mcp
- GitHub Stars
- 6
- Server Listing
- PreClick MCP Server
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.2/5.0
Tool DescriptionsA
Average 4.3/5 across 6 of 6 tools scored.
Server CoherenceA
Disambiguation3/5
The tools have clear distinctions between synchronous and asynchronous operations, but there is significant overlap: url_scanner_scan and url_scanner_scan_with_intent are nearly identical except for intent handling, and the async tools follow a similar pattern. This creates ambiguity about which to use in different scenarios, though descriptions help clarify.
Naming Consistency5/5
All tool names follow a consistent snake_case pattern with a clear prefix (url_scanner_) and descriptive suffixes (e.g., _async_scan, _async_task_result). The naming is highly predictable and uniform across all six tools, making it easy to understand their relationships.
Tool Count4/5
With 6 tools, the count is reasonable for a URL scanning service, covering both synchronous and asynchronous workflows. It might be slightly over-scoped due to the duplication between sync and async versions, but each tool serves a distinct operational purpose in the set.
Completeness5/5
The tool set provides complete coverage for URL scanning: it supports both synchronous and asynchronous scanning, with and without intent, plus status checking and result retrieval. There are no obvious gaps; agents can handle all expected workflows from submission to result retrieval.
Available Tools
6 toolsurl_scanner_async_scanRead-onlyInspect
Submit a URL for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_status to check progress, then url_scanner_async_task_result to get the scan result. Async counterpart of url_scanner_scan for clients without native MCP Tasks support.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to analyze. Must be HTTP or HTTPS. If no scheme provided, https:// is assumed. |
url_scanner_async_scan_with_intentRead-onlyInspect
Submit a URL with optional user intent for asynchronous security analysis. Returns immediately with a task_id. Poll with url_scanner_async_task_status to check progress, then url_scanner_async_task_result to get the scan result. Async counterpart of url_scanner_scan_with_intent for clients without native MCP Tasks support.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to analyze. Must be HTTP or HTTPS. If no scheme provided, https:// is assumed. | |
| intent | No | Optional user intent for visiting the URL. Recommended for additional context. |
url_scanner_async_task_resultRead-onlyInspect
Retrieve the result of an asynchronous scan task. If completed, returns the full scan result (risk_score, confidence, agent_access_directive, etc.). If still running, returns status with retry_after_ms — call again after that interval. Non-blocking.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | The task ID to retrieve the result for. |
url_scanner_async_task_statusRead-onlyInspect
Check the status of an asynchronous scan task. Returns the current task status using native MCP task semantics (working, completed, failed, cancelled) without blocking. Use url_scanner_async_task_result to retrieve the result once completed.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | The task ID to check status for. |
url_scanner_scanRead-onlyInspect
Analyze a URL for security threats (synchronous, blocks until complete or timeout). Returns risk score, confidence, agent access guidance, and intent_alignment (always not_provided for this tool; use url_scanner_scan_with_intent for intent context). For long-running scans, prefer url_scanner_async_scan which returns immediately with a task_id for polling via url_scanner_async_task_result.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to analyze. Must be HTTP or HTTPS. If no scheme provided, https:// is assumed. |
url_scanner_scan_with_intentRead-onlyInspect
Analyze a URL for security threats with optional user intent context (synchronous, blocks until complete or timeout). Returns risk score, confidence, agent access guidance, and intent_alignment. For long-running scans, prefer url_scanner_async_scan_with_intent which returns immediately with a task_id for polling via url_scanner_async_task_result.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The URL to analyze. Must be HTTP or HTTPS. If no scheme provided, https:// is assumed. | |
| intent | No | Optional user intent for visiting the URL. Recommended for additional context. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityBmaintenanceProtects AI agents from threats like prompt injection, jailbreaks, and SQL injection through a multi-layer scanning pipeline. It also enables PII redaction and rehydration to ensure data privacy during LLM interactions.Last updated124271Apache 2.0
TWZRD Agent Intelofficial
Alicense-qualityBmaintenancePre-spend trust layer for agents paying over x402 on Solana, providing seller vetting and readiness checks before USDC leaves the wallet.Last updated1MIT- Alicense-qualityBmaintenancePrivacy firewall for AI agents that scans files, commits, and push URLs to prevent sensitive data leaks.Last updatedMIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.