Drumbeats MCP

Official

by drumbeats-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Check SSL

check_ssl

Read-only

Checks a host's TLS/SSL certificate for expiry date and issuer. Identifies nearing expiration without requiring an account.

Instructions

Inspect a host's TLS/SSL certificate — validity, expiry date, and issuer. Works with no Drumbeats account or API key — useful for "is my SSL certificate about to expire?".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`port`	No	TLS port (default 443).
`hostname`	Yes	The hostname to inspect, e.g. example.com (no scheme).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`sans`	Yes
`error`	Yes
`valid`	Yes
`issuer`	Yes
`subject`	Yes
`checked_at`	Yes
`expires_at`	Yes
`valid_from`	Yes
`chain_valid`	Yes
`self_signed`	Yes
`check_region`	Yes
`port_checked`	Yes
`days_remaining`	Yes
`hostname_match`	Yes
`hostname_checked`	Yes
`signature_algorithm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Jul 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "chain_valid": {
+      "type": "boolean"
+    },
+    "check_region": {
+      "type": "string"
+    },
+    "checked_at": {
+      "type": "string"
+    },
+    "days_remaining": {
+      "anyOf": [
+        {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "expires_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "hostname_checked": {
+      "type": "string"
+    },
+    "hostname_match": {
+      "type": "boolean"
+    },
+    "issuer": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "port_checked": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "sans": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "self_signed": {
+      "type": "boolean"
+    },
+    "signature_algorithm": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "subject": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "valid": {
+      "type": "boolean"
+    },
+    "valid_from": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "ok",
+    "valid",
+    "issuer",
+    "subject",
+    "sans",
+    "expires_at",
+    "valid_from",
+    "days_remaining",
+    "chain_valid",
+    "self_signed",
+    "hostname_match",
+    "signature_algorithm",
+    "error",
+    "hostname_checked",
+    "port_checked",
+    "checked_at",
+    "check_region"
+  ],
+  "type": "object"
+}

Addedv0.1.1Jul 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. Description reinforces no authentication requirement and explains what the tool inspects, adding value beyond annotations.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose and immediate utility. No unnecessary words.

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

Completeness4/5

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

Given output schema exists, description covers key return aspects (validity, expiry, issuer) and use case. Sufficient for a simple inspection tool.

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 coverage is 100% with descriptions for both parameters. Description adds no additional detail beyond the schema, so baseline 3 is appropriate.

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?

Clearly states 'Inspect a host's TLS/SSL certificate' with specific details like validity, expiry date, and issuer. Distinct from sibling tools like check_dns and check_http.

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?

Indicates no account/API key needed and provides a common use case ('Is my SSL certificate about to expire?'). Lacks explicit guidance on when not to use, but context is clear.

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

Deploy Server