Certindex MCP Server

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

Remote serverstreamable-httpPython

What is the Certindex MCP server?

Certificate Transparency search for AI agents: certs, subdomains, issuance history, expiry. That is what the certindex mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

CertIndex indexes the full public CT corpus (~5 M certificates, growing ~100 k/day). This server wraps the public CertIndex REST API so an LLM can ask questions like:

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 10 tools. What each one is for:

  • search_certificates — Search the CT index by domain, CN, issuer, SAN, validity, or wildcard status
  • get_certificate — Fetch a single cert by SHA-256 fingerprint
  • get_domain_certificates — Every cert ever issued for an exact domain
  • get_subdomains — Enumerate unique subdomains seen in CT
  • get_latest_cert — Most recent currently-valid cert for a domain
  • get_expiring_certs — Certs for a domain expiring within days days
  • submit_global_sweep — Submit an async, domain-less CN/SAN substring sweep of the entire index (POST /v1/sweeps)
  • get_sweep_results — Poll a sweep job and paginate its results when done (GET /v1/sweeps/{id})
  • get_usage — Caller's tier, current usage, remaining quota, and entitlements
  • get_historical_backfill_status — Check / start the paid deep-history backfill for a domain

What it needs from you

Configuration is passed through the environment: CERTINDEX_API_KEY, CERTINDEX_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Certindex.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Certindex's toolset — search_certificates, get_certificate, get_domain_certificates and 7 more — is a fair guide to whether it matches your workflow. It is maintained by certindex; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
search_certificatesSearch the CT index by domain, CN, issuer, SAN, validity, or wildcard status.
get_certificateFetch a single cert by SHA-256 fingerprint.
get_domain_certificatesEvery cert ever issued for an exact domain.
get_subdomainsEnumerate unique subdomains seen in CT.
get_latest_certMost recent currently-valid cert for a domain.
get_expiring_certsCerts for a domain expiring within days days.
submit_global_sweepSubmit an async, domain-less CN/SAN substring sweep of the entire index (POST /v1/sweeps).
get_sweep_resultsPoll a sweep job and paginate its results when done (GET /v1/sweeps/{id}).
get_usageCaller's tier, current usage, remaining quota, and entitlements.
get_historical_backfill_statusCheck / start the paid deep-history backfill for a domain.

How to install the Certindex MCP server

{
  "mcpServers": {
    "certindex": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/inspector"],
      "env": {
        "CERTINDEX_API_KEY": "your-value",
        "CERTINDEX_BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CERTINDEX_API_KEYCredential the server authenticates with.Yes
CERTINDEX_BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Certindex to search certificates.
  • Use Certindex to get certificate.
  • Use Certindex to get domain certificates.

Frequently asked questions

It connects Certindex to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (search_certificates, get_certificate, get_domain_certificates, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Certindex directly.