Skip to main content
Glama
OrtaMarco

domain-security-mcp-server

by OrtaMarco

SSL/TLS Certificate Inspector

ssl_certificate
Read-onlyIdempotent

Retrieve and analyze the TLS certificate served by a host: issuer, subject, validity period, days until expiry, SANs, serial, and SHA-256 fingerprint. Identifies expired or soon-to-expire certificates.

Instructions

Inspect the TLS certificate served by a host: issuer, subject, validity window, days-until-expiry, SANs, serial and SHA-256 fingerprint. Flags expired or soon-to-expire certificates.

Args:

  • domain (string): host to connect to.

  • port (number): TLS port (default 443).

  • response_format ('markdown' | 'json'): output format (default 'markdown').

Returns: certificate fields plus { days_until_expiry, expired, expires_soon }.

Example: "When does github.com's certificate expire?" -> ssl_certificate(domain="github.com"). Errors: returns an error if the host is unreachable or serves no certificate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain (or host) to inspect, e.g. 'example.com'.
portNoTLS port (default 443).
response_formatNoOutput format: 'markdown' for a human-readable summary (default) or 'json' for the full structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYes
portYes
subject_common_nameNo
subject_alt_namesYes
issuer_organizationNo
issuer_common_nameNo
valid_fromNo
valid_toNo
days_until_expiryNo
expiredYes
expires_soonYes
serial_numberNo
fingerprint_sha256No
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the tool is safe. The description adds value by detailing what is returned (expiry flags, error on unreachable host) without contradicting annotations.

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?

The description is well-organized with clear sections (purpose, args, returns, example, errors). Each sentence serves a purpose, though slightly verbose in listing args.

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 the output schema exists, the description appropriately focuses on key return fields and error conditions. It covers necessary context for the tool's usage.

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?

Schema description coverage is 100%, so parameters are well-documented. The description supplements with default values and an example call, enhancing understanding beyond the schema.

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?

The description explicitly states the tool inspects TLS certificates from a host and lists specific fields (issuer, subject, validity, etc.). It clearly distinguishes itself from sibling tools like dns_lookup or whois_lookup, which serve different purposes.

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?

The description provides a clear use case with an example ('When does github.com's certificate expire?') and indicates when the tool is appropriate. It does not explicitly mention alternatives but the context of sibling tools makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrtaMarco/domain-security-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server