# Crtsh (npm · @pipeworx/mcp-crtsh)

crt.sh — Certificate Transparency log search

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 63/100, [markdown](https://verifymcp.io/servers/pipeworx-io-crtsh/crtsh-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-crtsh/crtsh-mcp)
- npm · `@pipeworx/mcp-crtsh`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-crtsh/pipeworx-mcp-crtsh.md), [page](https://verifymcp.io/servers/pipeworx-io-crtsh/pipeworx-mcp-crtsh)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-crtsh`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-crtsh).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 533 tokens (~266/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Crtsh MCP server?

Crtsh runs locally as an npm package, launched with npx -y @pipeworx/mcp-crtsh. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-crtsh -- npx -y @pipeworx/mcp-crtsh
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-crtsh": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crtsh"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-crtsh": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crtsh"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-crtsh -- npx -y @pipeworx/mcp-crtsh
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-crtsh": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-crtsh"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-crtsh --command npx --arg -y --arg @pipeworx/mcp-crtsh
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-crtsh:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-crtsh"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-crtsh": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-crtsh"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-crtsh -t stdio -c npx -a -y @pipeworx/mcp-crtsh
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-crtsh": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crtsh"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 65, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (2)

### `crtsh_search_domain` (~274 tokens)

"Find subdomains of [domain]" / "what TLS certificates exist for [domain]" / "certificate transparency for [host]" / "who issued the cert for [site]" — every certificate ever logged to the public Certificate Transparency logs for a domain and (by default) its subdomains, from crt.sh. AUTHORITATIVE for subdomain discovery and certificate inventory: CAs are required to log every certificate they issue, so this finds hosts that appear in no DNS zone transfer and no web crawl. Returns issuer, validity window, serial number and the full SAN list per certificate, plus a de-duplicated list of every hostname seen. PREFER OVER WEB SEARCH for "what hostnames does this organisation have" and for spotting mis-issued or forgotten certificates.

Input parameters:

- `domain` (string, required): Domain to search, e.g. "cloudflare.com". Do not include a scheme or a leading wildcard.
- `exclude_expired` (boolean): Return only certificates that have not passed their notAfter date. Default false (full history).
- `include_subdomains` (boolean): Search "%.domain" (every subdomain) as well as the domain itself. Default true.
- `limit` (number): Maximum certificates to return, 1-1000. Default 100. crt.sh returns newest-first once sorted here.

### `crtsh_certificate` (~206 tokens)

"Show me certificate [crt.sh id]" / "get the PEM for cert [id]" / "which certificate has serial [hex]" — fetch one logged certificate from crt.sh by its crt.sh id or by its hex serial number. Returns the PEM body plus the logged metadata (issuer, common name, SANs, validity window). Use after crtsh_search_domain to pull the actual certificate for inspection, or to identify a certificate you only have a serial number for (e.g. from a CA revocation notice or a TLS error log).

Input parameters:

- `id` (number): crt.sh certificate id, as returned in the "id" field by crtsh_search_domain.
- `include_pem` (boolean): Include the base64 PEM body. Default true.
- `serial` (string): Certificate serial number in hex, e.g. "06b6e2677b20b8aa16af09f498667be23ead". Either id or serial is required.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-crtsh/pipeworx-mcp-crtsh#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 65
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Crtsh MCP server?

Crtsh is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crtsh. crt.sh, Certificate Transparency log search. This page covers its npm package (@pipeworx/mcp-crtsh).

### Is the Crtsh MCP server safe to use?

Crtsh scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Crtsh MCP server expose?

Crtsh exposes 2 tools: crtsh_search_domain, crtsh_certificate. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.

### Is the Crtsh MCP server still maintained?

Crtsh is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Crtsh MCP server under?

Crtsh declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-crtsh
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-crtsh
- Repository: https://github.com/pipeworx-io/mcp-crtsh
- Website: https://pipeworx.io/packs/crtsh
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-crtsh/pipeworx-mcp-crtsh.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-crtsh/pipeworx-mcp-crtsh.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-crtsh/pipeworx-mcp-crtsh