Crtsh
NPM · @PIPEWORX/MCP-CRTSH · 2 COMPONENTS
crt.sh — Certificate Transparency log search
Available components
Last scanned (1 hour ago)
Scores higher than 72% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-crtsh). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-crtsh@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-crtsh |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-crtsh/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612306972 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bcc51eb3e9aa3e00e896994c1724a1e7424daea287c65b248294c780bc4261991f73adfe4e792815f1d218a8fc9f50fb7f91038467aa0537d29a9b383 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
crtsh_certificate ~206
"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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
crtsh_search_domain ~274
"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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-crtsh
claude mcp add pipeworx-io-crtsh -- npx -y @pipeworx/mcp-crtsh
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.