Skip to main content
Glama

Security Scan - outdated libraries with CVEs, SSL, headers, email spoofing

security_scan
Read-onlyIdempotent

External security scan of a website: detects JavaScript libraries and frameworks with their versions and lists their known vulnerabilities (OSV.dev + CISA KEV exploited flag + fix version), security headers + SSL grade and DMARC/SPF spoofing grade. Passive, no intrusive probing. ~2-6 s. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/security-scan.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "jquery.com"
    },
    "name": "security_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesWebsite domain, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent and openWorld, and the description adds real context beyond them: operations are passive with no intrusive probing, runtime is ~2-6 s, and there are hard quota and billing constraints (25 calls/day per IP free, $0.01/call via x402 with the endpoint URL). Those quota and payment details are exactly the kind of information annotations cannot carry and that change whether an agent should call the tool at all.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core capability, then supporting detail in descending priority (detections, passivity, latency, quota, pricing). It is dense but every clause carries information. Minor deduction for the run-on second sentence where headers/SSL and DMARC/SPF are packed together without clear separation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by enumerating what will be reported, including the enrichment fields (KEV flag, fix version) an agent would otherwise have to discover empirically. Combined with the passivity, latency, quota and pricing notes, nothing critical for deciding or calling correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter and schema description coverage is 100%, with the schema already supplying an example (example.com) for `domain`. The description adds nothing further about input format, TLD handling or whether subdomains are accepted. With one fully documented parameter, the baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("External security scan of a website") and enumerates what it returns: JS library versions, known CVEs with OSV.dev/CISA KEV/fix version, security headers, SSL grade, DMARC/SPF grade. That is far more specific than the title alone. It does not, however, contrast itself with lookalike siblings such as domain_security_report, email_auth, osv_vulns or website_report, so an agent must infer which overlapping scan to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: it is a per-domain scan with a stated cost and time budget, which helps an agent decide whether to call it. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for the email-auth or vulnerability-only cases covered by siblings. Prerequisites beyond a domain are unstated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources