mcpbeat Sign in

CTlogs.io MCP Server

answering

CTlogs.io is answering right now. Last checked 3 min ago. Last commit 5 Sep 2026.

Certificate Transparency search: subdomains, certificate history and hostname keyword search.

Uptime history 62 days of history · worst day 42%
62 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
458 ms
Response time
average over 24h
0
Stars
last commit 5 Sep 2026

CTlogs.io missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add ctlogs --transport http https://mcp.ctlogs.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.ctlogs.io/mcp
~/.codex/config.toml
[mcp_servers.ctlogs]
url = "https://mcp.ctlogs.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ctlogs": {
      "url": "https://mcp.ctlogs.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "ctlogs": {
      "type": "http",
      "url": "https://mcp.ctlogs.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.ctlogs.io/mcp streamable-http sign-in 390 ms 3 min ago

Alternatives to CTlogs.io

same job, measured the same way
Certindex MCP
by certindex

Certificate Transparency search for AI agents: certs, subdomains, issuance history, expiry.

127 installs/wk local only
Crtsh
by pipeworx-io

crt.sh — Certificate Transparency log search

471 installs/wk 46 tools answering
recon
by blisspixel

Public DNS, certificate transparency, and identity observations.

3 285 installs/wk local only
who.is
by who

Parsed WHOIS, RDAP, DNS, certificates, nameservers and domain history for any domain.

answering
Certspotter MCP
by mrfentmen

Certificate transparency lookups from Cert Spotter. No key required.

157 installs/wk local only
Google Ads Transparency
by dataleadspro

Query Google Ads Transparency data: advertiser suggestions, creatives, and ad history.

4 tools answering
MCP Substack Scraper
by mambabuilt

Substack publications, posts, subscriber counts, and keyword search.

305 installs/wk local only
SSL Certificate Check
by powmcp

Inspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions.

1 tools answering

CTlogs.io — questions

Answers built from our own checks of this server.

Why is there no tool list for CTlogs.io?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is CTlogs.io working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 458 ms. The bar chart above shows every period we have measured.
How do I connect CTlogs.io?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to CTlogs.io?
No API key is involved. CTlogs.io answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is CTlogs.io?
It answers our handshake in 458 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is CTlogs.io open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.