Drumbeats MCP

Official

by drumbeats-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

Check SSL

check_ssl

Read-only

Inspect a host's TLS/SSL certificate to check validity, expiry date, and issuer, answering "is my SSL certificate about to expire?" without needing an account or API key.

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

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

Output 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.

Changed12 schema fields changedv0.5.1Oct 27, 2026

removedOutput schema / properties / error / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / error / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / expires_at / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / expires_at / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / issuer / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / issuer / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / signature_algorithm / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / signature_algorithm / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / subject / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / subject / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / valid_from / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / valid_from / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description doesn't need to restate read-only safety. It adds genuinely new context beyond annotations: the no-account/no-API-key auth model and the specific certificate fields inspected. It doesn't mention rate limits or failure behavior for unresolvable hosts, which keeps it below a 5.

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 short sentences, front-loaded with the verb and resource, then the differentiator (no account required) and a concrete motivating use case. Every clause earns its place with no filler.

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?

The tool is simple (one required param, output schema present), and the description covers purpose, scope of inspection, and auth model. Return values are covered by the output schema, so little is missing; only edge-case behavior (invalid host, timeout) is absent.

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%, with hostname ('no scheme') and port (default 443) fully documented in the schema. The description adds no parameter-level guidance, so the baseline of 3 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 (inspect a host's TLS/SSL certificate) and enumerates what is checked: validity, expiry, issuer. It is clearly distinguishable from the sibling check_http and check_dns by resource, though it never names those siblings explicitly.

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?

Provides a concrete usage scenario ('is my SSL certificate about to expire?') and the key eligibility fact that no Drumbeats account or API key is needed, which tells the agent it can call this unauthenticated. It stops short of stating when to prefer check_http or other alternatives.

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