Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Certificate Transparency search: subdomains, certificate history and hostname keyword search.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.ctlogs.io/mcpRun this in your terminal
claude mcp add --transport http ctlogs https://mcp.ctlogs.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ctlogs": {
"url": "https://mcp.ctlogs.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"ctlogs": {
"type": "http",
"url": "https://mcp.ctlogs.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.ctlogs.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account ABTdomain, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Certificate Transparency, inside the conversation you are already having.
CTlogs.io runs a hosted Model Context Protocol server. Connect it to Claude, Cursor, or any client that speaks MCP, and your assistant can query the certificate index itself: which certificates have been issued for a hostname, by which certificate authority, and when they expire; or which certificate sits behind a fingerprint. You ask; it looks it up; you work with what comes back.
https://mcp.ctlogs.io/mcp
It is the same index and the same account you use on ctlogs.io. What changes is who does the typing.
You need a CTlogs account with an active plan. Plans and allowances are on the pricing page.
Every client wants the same two things: the server address above, added as a remote or HTTP connector, and a sign-in. The client opens CTlogs in your browser, you sign in and approve the connection once. There is no key to copy and nothing to keep in a configuration file.
claude mcp add --transport http ctlogs https://mcp.ctlogs.io/mcp
Then run /mcp inside Claude Code to complete the sign-in.
Settings, then Connectors, then *Add custom connector*. Name it CTlogs, paste the server address, and follow the sign-in prompt.
Add the server to your MCP settings (.cursor/mcp.json in a project, or the global file):
{
"mcpServers": { "ctlogs": { "url": "https://mcp.ctlogs.io/mcp" } } }
Cursor offers the sign-in when it first connects to the server.
Any client that supports MCP over Streamable HTTP with OAuth sign-in works the same way.
| Tool | The question it answers |
|---|---|
lookup_certificates | The certificate history of one hostname, or the certificate behind a fingerprint |
index_status | How large and how fresh the index is |
account_quota | How much of your allowance is left |
Listing the subdomains of a domain and searching hostnames for a keyword are DomainKits tools, from the same team; this server answers one question, which certificates exist for a name.
Every tool is read-only. Nothing the assistant can call changes anything.
The tools describe their own parameters to the client, so your assistant already knows how to call them. Current allowances and limits are on the pricing page and in the API documentation; they are not repeated here because they will change as the service settles in.
CTlogs.io is built on the technology behind ABTdomain.com, the domain intelligence platform, and shares its data and tooling with Domainkits.com, which covers domain search and newly registered domains. Certificate Transparency is one lens on the same picture: names appear in the domain registries, in DNS, and in the certificate logs, and the three sites look at the same names from those three sides.
Open source tools and datasets from the same team are on github.com/ABTdomain.
Questions and problems: info@lyalpha-gmbh.com, or open a ticket from the member area.
CTlogs.io is operated by Lyalpha GmbH, Düsseldorf, Germany. Terms · Privacy · Imprint