Skip to main content
Glama

URL Scanner Online by Aprensec — URL & Domain Security Scanner

Server Details

Scan any URL, domain, or IP address for security threats using URLScanner.online.

Returns a full security report including:

Threat verdict (safe / suspicious / malicious) and 0–100 security score
Threat intelligence across 70+ feeds (malware, phishing, blocklists)
SSL certificate validity, expiry, issuer, and OCSP status
HTTP security headers audit (missing / misconfigured)
DNS records (A, AAAA, MX, TXT, NS, SOA)
And More!

Free to use. No account required. 10 scans/day

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL

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 DescriptionsA

Average 4.5/5 across 2 of 2 tools scored.

Server CoherenceA
Disambiguation5/5

The two tools have completely distinct purposes: scan_url initiates a new security scan, while get_scan retrieves results for an existing scan ID. There is no functional overlap or ambiguity in selection.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (scan_url, get_scan) using snake_case. The action verbs clearly indicate initiation vs. retrieval, establishing a predictable naming convention.

Tool Count3/5

With only 2 tools, this falls into the 'borderline thin' category per the rubric. While it covers the absolute minimum submit-and-retrieve workflow, the lack of auxiliary operations (list scans, check rate limits) makes the surface feel sparse for managing the stated 10-scan daily quota.

Completeness3/5

The CRUD surface is minimal: only Create (scan) and Read (get result) are supported. Notable gaps include the inability to list recent scans (relevant given 1-hour retention), check remaining rate limit quota, or cancel in-progress scans—operations agents would need to avoid burning the strict 10-scan daily allowance.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources