`crtsh_certificate`

Pack: crtsh · Endpoint: https://gateway.pipeworx.io/crtsh/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/crtsh_certificate for the schema, then POST the same URL with its arguments for the data.

“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).

Parameters

Name	Type	Required	Description
`id`	number	no	crt.sh certificate id, as returned in the “id” field by crtsh_search_domain.
`serial`	string	no	Certificate serial number in hex, e.g. “06b6e2677b20b8aa16af09f498667be23ead”. Either id or serial is required.
`include_pem`	boolean	no	Include the base64 PEM body. Default true.

Example call

Arguments

{
  "serial": "061610ef41aa5f79065c5fa4bb838dc6"
}

curl

curl -X POST https://gateway.pipeworx.io/crtsh/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"crtsh_certificate","arguments":{"serial":"061610ef41aa5f79065c5fa4bb838dc6"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('crtsh_certificate', {
  "serial": "061610ef41aa5f79065c5fa4bb838dc6"
});

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "crtsh": {
      "url": "https://gateway.pipeworx.io/crtsh/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

crtsh_certificate