certindex-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CERTINDEX_API_KEY | Yes | Your CertIndex API key. Mint one at https://ctindex.io/app/keys | |
| CERTINDEX_TIMEOUT | No | Per-request HTTP timeout (seconds) | 30 |
| CERTINDEX_BASE_URL | No | Override for self-hosted deployments / staging | https://api.ctindex.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_certificatesA | Search the CT certificate index by domain, CN, issuer, SAN,
validity, or wildcard status. Returns a |
| get_certificateA | Fetch a single cert by its 64-char hex SHA-256 fingerprint. Set |
| get_domain_certificatesA | List certificates for an exact domain name. Cold domains
return a Set |
| get_subdomainsB | Enumerate unique subdomains seen in CT logs. |
| get_latest_certA | Most recently issued cert for a domain (or Set |
| get_expiring_certsB | Certificates for |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: fetching a single certificate by fingerprint, listing certificates for a domain, finding expiring certs, getting the latest cert, enumerating subdomains, and performing a general search. No ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_certificate, get_domain_certificates). The naming is predictable and clear.
With 6 tools covering the core operations of a certificate index (fetch, list, search, subdomain enumeration), the count is well-scoped and not excessive.
The set covers the main operations expected from a CT log index: retrieval by fingerprint, domain listing, expiry checks, latest cert, subdomain enumeration, and general search. Minor gaps like raw log entry access are not critical for the stated purpose.