ctlogs.dev — Certificate Transparency search
REMOTE · MCP.CTLOGS.DEV
Search Certificate Transparency logs: subdomains, TLS certificates, organizations, CAs.
Available components
Last scanned (16 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 982 tokens (~196/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.ctlogs.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ctlogs.dev | CN=YE2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6f955d11b9aafdc0d74df3c2072012a94d1 |
| SANs: *.ctlogs.dev, ctlogs.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ctlogs.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| ctlogs.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ctlogs.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ctlogs.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_subdomains Find subdomains ~175
List the hostnames found under a domain in TLS certificates: one row per hostname with the number of certificates and first/last seen dates. Covers certificates valid now or expired within the last 90 days; set history to true for every hostname certified since 2013 (needs an API key on the Pro Lite or Pro plan). Use this to enumerate subdomains; use search_certificates for the certificates themselves.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The next_cursor of the previous call, to get the next page; omit for the first page |
| domain | string | yes | A bare DNS name such as example.com, without a scheme, path or port |
| history | boolean | – | true lists every hostname certified since 2013 instead of the last 90 days; needs an API key on the Pro Lite or Pro plan |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| domain | string | yes | – |
| has_more | boolean | yes | – |
| hosts | null|array | yes | – |
| next_cursor | string | – | – |
| scope | string | yes | – |
No examples provided.
get_ca Get issuing CA ~122
Return one issuing CA certificate by its SHA-256 fingerprint (the issuer_ca field of get_certificate): subject, issuer, validity, parent and cross-signed certificates, the number of certificates it issued and a page of them.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The next_cursor of the previous call, to get the next page; omit for the first page |
| limit | integer | – | Issued certificates per call, 1 to 100; default 25 |
| sha256 | string | yes | SHA-256 fingerprint of the CA certificate, 64 hex characters |
| Name | Type | Req | Description |
|---|---|---|---|
| first_seen | string | yes | – |
| has_more | boolean | yes | – |
| issued | null|array | yes | – |
| issued_count | string | yes | – |
| issuer_dn | string | yes | – |
| next_cursor | string | – | – |
| not_after | string | yes | – |
| not_before | string | yes | – |
| parents | null|array | yes | – |
| pubkey_sha256 | string | yes | – |
| related | null|array | yes | – |
| self_signed | boolean | yes | – |
| serial_hex | string | yes | – |
| sha256 | string | yes | – |
| subject_dn | string | yes | – |
No examples provided.
get_certificate Get certificate ~91
Return the full record of one certificate: subject, issuer, serial number, validity, DNS names, key and signature details, the CT log entries that recorded it and download URLs for the certificate body. id is the id field of a search result or the certificate's SHA-256 fingerprint (64 hex characters).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A search-result id or a 64-hex SHA-256 fingerprint |
| Name | Type | Req | Description |
|---|---|---|---|
| downloads | null|array | yes | – |
| ext_key_usage | null|array | yes | – |
| final_first_seen | string | – | – |
| final_sha256 | string | – | – |
| id | string | yes | – |
| is_ca | boolean | yes | – |
| issuer_ca | string | – | – |
| issuer_dn | string | yes | – |
| log_entries | null|array | yes | – |
| log_entries_total | integer | yes | – |
| not_after | string | yes | – |
| not_before | string | yes | – |
| policy_oids | null|array | yes | – |
| precert_first_seen | string | – | – |
| precert_sha256 | string | – | – |
| pubkey_sha256 | string | – | – |
| san_dns | null|array | yes | – |
| san_more | integer | yes | – |
| serial_hex | string | yes | – |
| sig_algo | string | – | – |
| subject_dn | string | yes | – |
No examples provided.
search_certificates Search certificates by domain ~260
List TLS certificates issued for a domain name: id, matching names, issuer, serial number and validity dates. By default matches the exact name; set include_subdomains to true to also match every name under it. Covers certificates valid now or expired within the last 90 days unless archive is set to "full" or a year from 2013 (needs an API key on the Pro plan). Pass a row's id to get_certificate for the full record. To list hostnames rather than certificates, use find_subdomains.
| Name | Type | Req | Description |
|---|---|---|---|
| archive | string | – | "full" for all certificates since 2013, or a four-digit year from 2013 for certificates valid into that year or later; needs an API key on the Pro plan. Omit for certificates valid now or expired wit… |
| cursor | string | – | The next_cursor of the previous call, to get the next page; omit for the first page |
| domain | string | yes | A bare DNS name such as example.com, without a scheme, path or port |
| include_subdomains | boolean | – | true also matches every name under the domain |
| limit | integer | – | Rows per call, 1 to 100; default 25 |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| has_more | boolean | yes | – |
| history_truncated | boolean | – | – |
| history_window_days | integer | – | – |
| next_cursor | string | – | – |
| rows | null|array | yes | – |
No examples provided.
search_organization Search certificates by organization ~221
List TLS certificates whose subject organization matches a name, e.g. "PayPal, Inc.": id, subject common name, domains, issuer and validity dates. Covers certificates valid now or expired within the last 90 days unless archive is set to "full" or a year from 2013 (needs an API key on the Pro plan). One call counts as 10 requests against the rate limit.
| Name | Type | Req | Description |
|---|---|---|---|
| archive | string | – | "full" for all certificates since 2013, or a four-digit year from 2013 for certificates valid into that year or later; needs an API key on the Pro plan. Omit for certificates valid now or expired wit… |
| cursor | string | – | The next_cursor of the previous call, to get the next page; omit for the first page |
| limit | integer | – | Rows per call, 1 to 100; default 25 |
| name | string | yes | Organization name as it appears in the certificate subject, e.g. "PayPal, Inc." |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| has_more | boolean | yes | – |
| history_truncated | boolean | – | – |
| history_window_days | integer | – | – |
| next_cursor | string | – | – |
| rows | null|array | yes | – |
No examples provided.
How do I install the ctlogs.dev — Certificate Transparency search MCP server?
ctlogs.dev — Certificate Transparency search is a hosted endpoint at https://mcp.ctlogs.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.ctlogs.dev
claude mcp add --transport http dev-ctlogs-certificate-transparency 'https://mcp.ctlogs.dev/mcp'
What is the ctlogs.dev — Certificate Transparency search MCP server?
ctlogs.dev — Certificate Transparency search is an MCP server listed in the public MCP registry as dev.ctlogs/certificate-transparency. Search Certificate Transparency logs: subdomains, TLS certificates, organizations, CAs. This page covers its hosted endpoint (https://mcp.ctlogs.dev/mcp).
Is the ctlogs.dev — Certificate Transparency search MCP server safe to use?
ctlogs.dev — Certificate Transparency search scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ctlogs.dev — Certificate Transparency search MCP server expose?
ctlogs.dev — Certificate Transparency search exposes 5 tools: find_subdomains, get_ca, get_certificate, search_certificates, search_organization. Their descriptions and schemas cost roughly 869 tokens of context every time the server is loaded.
Does the ctlogs.dev — Certificate Transparency search MCP server require authentication?
No. We connected to ctlogs.dev — Certificate Transparency search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ctlogs.dev — Certificate Transparency search MCP server still maintained?
ctlogs.dev — Certificate Transparency search is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ctlogs.dev — Certificate Transparency search MCP server?
VerifyMCP ran 12 checks on ctlogs.dev — Certificate Transparency search, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ctlogs.dev — Certificate Transparency search: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.