MCP.Market

Certindex MCP server

by certindex·io.github.certindex/certindex-mcp·v0.2.0
No reviews yet

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

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Certindex yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Certindex tools (10, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_certificate

    Fetch a single cert by its 64-char hex SHA-256 fingerprint.

  • get_domain_certificates

    List certificates for an exact domain name. Cold domains return a ``backfill_status`` sentinel; retry per the hint.

  • get_expiring_certs

    Certificates for ``domain`` expiring within ``days`` days.

  • get_historical_backfill_status

    Check — and, when entitled, start or resume — the paid deep-historical certificate backfill for a domain.

  • get_latest_cert

    Most recent CURRENTLY-VALID cert for a domain (or ``{cert: null}`` with a backfill sentinel on cold domains).

  • get_subdomains

    Enumerate unique subdomains seen in CT logs.

  • get_sweep_results

    Poll an async sweep job by id; paginate its bounded result set once the job completes.

  • get_usage

    Return the caller's tier, current usage, remaining quota, billing period boundary, and add-on entitlements — lets an agent budget its own calls. Not rate-limited.

  • search_certificates

    Search the CT certificate index by domain, CN, issuer, SAN, validity, or wildcard status. Returns a ``has_more`` boolean for paging (no unbounded COUNT).

  • submit_global_sweepwrite action

    Submit an asynchronous GLOBAL (domain-less) CN/SAN substring sweep of the entire index as a background job — the escape hatch when a global search exceeds the synchronous query budget.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 58 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Certindex compares

Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 3,470 Web search servers
Tools
10
the typical Web search server has 5
Tools that change things
10%
typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 9 read · 1 change

Install Certindex in Claude Code, Cursor or VS Code

claude mcp add certindex-mcp -- uvx certindex-mcp
Add to Cursor

What the publisher says

From the Certindex repository's README, as published. We do not edit it. Read it on GitHub

certindex-mcp

<!-- mcp-name: io.github.certindex/certindex-mcp -->

An MCP (Model Context Protocol) server that exposes CertIndex's Certificate Transparency search tools to any MCP-compatible client (Claude Desktop, the MCP Inspector, Continue, etc.).

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:

  • "List every TLS certificate ever issued for example.com."
  • "What subdomains has Let's Encrypt seen for mycompany.io?"
  • "Show me certs expiring in the next 30 days for api.mycompany.io."
  • "Pull the full PEM and CT log metadata for SHA-256 ."

Why this repo exists

The CertIndex monorepo bundles an MCP server (mounted at https://api.ctindex.io/mcp) that talks directly to the production Postgres index. This standalone package is a thin client-side shim: it speaks MCP to your editor / agent and forwards every tool call to the hosted CertIndex REST API over HTTPS. Two consequences:

at https://ctindex.io and you're done.

  1. You don't need a copy of the index — sign up for a free API key

pydantic) — easy to audit, easy to vendor, no DB drivers.

  1. The package has a tiny dependency footprint (mcp, httpx,

Install

pip install certindex-mcp

Or with uvx for one-shot use:

uvx certindex-mcp

To install the latest development version from source instead:

pip install git+https://github.com/certindex/certindex-mcp

Quickstart — Claude Desktop

Add to ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows):

{
  "mcpServers": {
    "certindex": {
      "command": "uvx",
      "args": ["certindex-mcp"],
      "env": {
        "CERTINDEX_API_KEY": "ctx_live_..."
      }
    }
  }
}

Restart Claude Desktop. The ten CertIndex tools appear in the tool tray.

Tools

Ten tools, matching the hosted CertIndex MCP server 1:1:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Certindex: common questions

Is Certindex MCP server safe?
Mostly: it is graded B (75/100). Read the Certindex safety report
How do I install Certindex?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Certindex need an API key?
Yes. The registry entry asks for CERTINDEX_API_KEY.
Is Certindex maintained?
The last commit was 99 days ago (2026-07-28). The latest release is v0.2.0.
How does Certindex compare with other Web search MCP servers?
safety score 75/100 (higher than 45% of 3,470 Web search servers); tools 10 (the typical Web search server has 5); tools that change things 10% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.