Connect CTlogs to Claude, Cursor, or any client that speaks the Model Context Protocol. Ask in the conversation you are already having, and the answer comes from the live index.
The Model Context Protocol is an open standard for connecting AI assistants to outside tools. We run a server that speaks it, so instead of you searching, copying rows and pasting them into a chat, the assistant queries the certificate index itself, mid-conversation, and works with what comes back.
It is the same data behind the same account you already have. What changes is who does the typing.
https://mcp.ctlogs.io/mcp into your client’s connector settings.claude mcp add --transport http ctlogs https://mcp.ctlogs.io/mcpOther clients word it differently, but they all want the same thing: the server address above, added as a remote or HTTP connector. The sign-in step is the same everywhere.
| Tool | The question it answers |
|---|---|
| find_subdomains | Which subdomains of a domain exist in the record, and when each was last seen |
| lookup_certificates | The certificate history of one hostname, or the certificate behind a SHA-256 fingerprint |
| search_hostnames | Which hostnames contain a word, for impersonation and typosquat hunting |
| index_status | How large and how fresh the index is |
| account_quota | How much of your allowance is left this hour |
Every one of them is read-only. Nothing the assistant can call changes anything.
The client is authorised through your CTlogs account. It never sees your API key, so no secret ends up sitting in a configuration file on a laptop.
A laptop, an editor and a server can all be connected at once. They act as the same account, and usage is counted once against the allowance you already have: a second client does not grant you a second allowance, and it does not cost you one either.
Each connection stands on its own. Cut off a machine you no longer use and everything else keeps working.
Twenty-five rows by default, a hundred at most. The reader is a context window, not a data pipeline; for bulk work, query the API directly.
You need a CTlogs account with an active plan. See what that includes, or sign in if you already have one.
An open standard for connecting AI assistants to outside tools and data. A client that speaks it can call a tool the moment a conversation needs it, instead of you moving results back and forth by hand.
No. You sign in from the client and approve the connection once.
Yes, as many as you like, all as the same account. Usage is counted once.
No. Every tool is read-only.
The same index the rest of the site uses. New certificates are ingested continuously as they appear in the logs.