Skip to main content
Glama

KillBounce Data

Certificate Transparency subdomain finder

certs
Read-onlyIdempotent

Every unexpired TLS certificate publicly logged for a domain (Certificate Transparency): all subdomains and wildcards found, issuing authorities with counts, certificates issued in the last 7 days, expiry dates, and flags such as sudden new issuance. Useful for mapping a domain's attack surface or spotting look-alike infrastructure. Price: $0.01 USDC on Base per successful call (x402).

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": "certs"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain to search (subdomains are included)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds substantial value beyond those annotations by listing returned data categories, recent-issuance flags, expiry information, and the x402 pricing model of $0.01 USDC on Base per successful call.

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 front-loaded with what the tool returns and is generally efficient, with no irrelevant filler. The first sentence is dense with enumerated output details, which is useful but could be slightly easier to scan.

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?

For a single-parameter, read-only lookup with rich annotations and no output schema, the description provides enough context to call and interpret the tool. It lists the main returned categories and pricing, though it does not describe response structure or failure/charging edge cases in detail.

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?

There is one parameter with 100% schema description coverage, and the schema already explains that the domain to search includes subdomains. The description does not add format guidance such as whether to pass a bare domain versus a URL, so it remains at the baseline level for a fully documented single parameter.

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?

The description clearly states the resource and scope: unexpired TLS certificates from Certificate Transparency for a domain, including subdomains and wildcards. It is specific enough to distinguish this from a general DNS lookup, but it does not explicitly differentiate itself from sibling tools such as dns or domainrisk.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives use cases (attack surface mapping and look-alike infrastructure detection) but does not specify when not to use it or name alternative tools. The guidance is implicit rather than explicit routing between this and sibling tools.

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