Skip to main content
Glama

Certificate transparency records for a domain

security_crtsh_certificate_transparency
Read-only

Certificate transparency records for a domain from the CertSpotter public CT index: certificate id, validity dates, revocation flag and the DNS names on each certificate (including subdomains). Shows issued certificates only, not live TLS configuration. crt.sh was unavailable during testing, so CertSpotter is used. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "domain": "<domain>"
    },
    "name": "security_crtsh_certificate_transparency"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax certificates, 1 to 50 (default 10)
domainYesDomain name, e.g. wikivoyage.org (letters, digits, dots, hyphens)

Output Schema

NameRequiredDescriptionDefault
countNo
domainNo
sourceNo
checkedAtNo
certificatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description adds substantial context they do not carry: the underlying index, subdomain inclusion, the coverage limit (issued certs, not active TLS), and a cost model stating $0.002 per successful call via x402 with failed calls uncharged. That pricing/charging semantics is exactly the sort of behavior an agent needs and no structured field provides.

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 purpose, then scope limits, then cost — a sensible order. Every clause carries information (the crt.sh note justifies why the tool name and provider diverge), though the payment-network enumeration is slightly heavy for a single sentence.

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?

An output schema exists, so return values need not be spelled out, yet the description still sets expectations about what is and isn't covered and what the call costs. For a two-parameter read tool with annotations, nothing needed for correct invocation is missing.

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% and both parameters are documented in the schema, including the limit range and default. The description adds no additional meaning about domain format or limit behavior, so the baseline of 3 applies.

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 resource (certificate transparency records) and scope (a domain), names the concrete data source (CertSpotter public CT index), and enumerates the returned fields. It also draws a sharp boundary against a related-but-different capability by saying it shows 'issued certificates only, not live TLS configuration'.

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 negative scoping ('not live TLS configuration') tells the agent when this is the wrong tool, and the crt.sh/CertSpotter note explains a provider discrepancy an agent might otherwise trip over. It lacks an explicit 'use this instead of X' alternative, but with unrelated siblings that gap is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources