TLS Checker Skill

Overview

TLS Check connects to the provided domain and port and runs a TLS handshake for each protocol version to determine which are supported. It identifies the highest negotiable version (like TLS 1.2/1.3), flags whether deprecated TLS 1.0/1.1 remain exposed, and returns a composite risk score summarizing the server's protocol security.

Live Test TLS Checker Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as TLSCheckerSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "TLSCheckerSkill",
  "arguments": {
    "domain": "amazon.com"
  }
}

You do not name the tool yourself; the model picks it. Asking about amazon.com in the terms this skill covers is enough for it to reach for TLSCheckerSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`domain`Required	string	The domain to check the TLS/SSL configuration for domain
`port`Optional	integer	The port to connect to (usually 443 for HTTPS) default 443 · range 1–65535

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "amazon.com",
    "tlsVersions": {
      "TLSv1": true,
      "TLSv1.1": true,
      "TLSv1.2": true,
      "TLSv1.3": true
    },
    "highestVersion": "TLSv1.3",
    "hasDeprecatedTLS": true,
    "isSecure": false,
    "riskScore": 55,
    "riskLevel": "medium"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`domain`	string	`amazon.com`	Domain name that was checked for TLS configuration
`tlsVersions`	object	`{…}`	Whether the server completes a handshake at each protocol version, keyed TLSv1, TLSv1.1, TLSv1.2 and TLSv1.3
`tlsVersions.TLSv1`	boolean	`true`	Whether TLS 1.0 protocol is supported by server
`tlsVersions.TLSv1.1`	boolean	`true`	Whether TLS 1.1 protocol is supported by server
`tlsVersions.TLSv1.2`	boolean	`true`	Whether TLS 1.2 protocol is supported by server
`tlsVersions.TLSv1.3`	boolean	`true`	Whether TLS 1.3 protocol is supported by server
`highestVersion`	string	`TLSv1.3`	The highest TLS version the server supports (e.g. TLSv1.3), or null if none were negotiable
`hasDeprecatedTLS`Premium	boolean	`true`	Whether the server still supports deprecated TLS 1.0 or 1.1, which are insecure and disallowed by PCI-DSS
`isSecure`Premium	boolean	`false`	Whether the server supports a modern TLS version (1.2/1.3) and does not expose any deprecated version
`riskScore`Premium	number	`55`	Composite 0-100 risk score based on missing modern TLS and exposure of deprecated protocols (higher is riskier)
`riskLevel`Premium	string	`medium`	Risk band derived from the score: low, medium or high

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Payment Gateway Auditing: Before onboarding merchant checkout domains, fintech compliance auditors check whether incoming endpoints accept legacy protocols like TLS 1.0 or 1.1.
Deployment Pipeline Verification: Flag outdated web server configurations during production releases by testing handshake support across all modern protocol versions before traffic switches over.
Attack Surface Scanning: Security analysts query customer-facing domains periodically to find legacy protocol support and review the highest negotiable version across exposed web ports.
Vendor Security Assessments: When evaluating SaaS suppliers, procurement teams inspect external hostnames to confirm that partner servers negotiate TLS 1.2 or 1.3.

Other ways to use TLS Checker Skill

Set up TLS Checker Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →