ScrapeMole Domains

ScrapeMole Domains: DNS, WHOIS/RDAP, domain availability, email security, SSL certificates and subdomains for AI agents: SSL/TLS certificate check

ssl

Read-onlyIdempotent

Use when you need to know whether a website or mail server has a valid HTTPS certificate or when it expires: opens a live TLS connection (SNI) to the host and returns whether the chain is publicly trusted (with the exact error, e.g. CERT_HAS_EXPIRED or self-signed), whether the certificate matches the hostname, validity dates and days remaining, subject, issuer, SAN list, key type, TLS protocol, cipher, ALPN and the certificate chain. Answers about the certificate even when it is invalid (that is the point); unreachable hosts are not charged. Hosts served by Cloudflare's own network cannot be probed live from our Workers; for those the response has live:false and shows the newest unexpired certificate logged for the host in Certificate Transparency (trusted:null). Paid tool: x402 USDC on Base, $0.003 per successful call; call without payment to receive the PaymentRequired object.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>"
    },
    "name": "ssl"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Hostname, e.g. github.com (no path).
`port`	No	TLS port: 443, 8443, 465, 993 or 995.	443

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: it explains that answers are returned even for invalid certificates, that unreachable hosts are not charged, the Cloudflare Workers limitation with live:false plus Certificate Transparency fallback and trusted:null, and the x402 USDC payment model with a PaymentRequired object.

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 usage trigger, then behavior, return fields, fallback path and pricing in a dense sequence. It is long and somewhat run-on, but nearly every clause adds operational value an agent needs.

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?

With no output schema, the description enumerates the returned fields (trust status, error codes, validity dates, subject, issuer, SAN, key type, protocol, cipher, ALPN, chain) and documents the degraded live:false response path, so an agent knows both what it gets and when results differ.

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

Parameters3/5

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

Schema description coverage is 100%, so host and port are already documented in the schema; the description adds only the SNI mechanism and confirms the host/port shape implicitly. Baseline 3 is appropriate since the schema carries the parameter burden.

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

Purpose5/5

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

States a specific verb and resource: it opens a live TLS connection to a host and reports certificate trust, hostname match, validity, chain and TLS parameters. It is clearly distinguishable from siblings like dns, rdap, availability and subdomains, which address different domain concerns.

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

Usage Guidelines4/5

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

Opens with an explicit trigger ('Use when you need to know whether a website or mail server has a valid HTTPS certificate or when it expires') and covers the mail-server case that overlaps with email_security. It does not name a sibling to route away from, but the selection condition is unambiguous.

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

All ScrapeMole Domains tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?