Remote MCP · Endpoint

Crtsh MCP server

No. Crtsh answered an MCP handshake 22 hours ago.

UpLast checked 22 hours ago

Server URL

https://gateway.pipeworx.io/crtsh/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/crtsh
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
60 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
crt.sh — Certificate Transparency log search
Listing
From the official MCP registry (active).
Recent checks of Crtsh
CheckedResultHandshake
22 hours agoHandshake completed60 ms
3 days agoHandshake completed56 ms
5 days agoHandshake completed59 ms
6 days agoHandshake completed52 ms
8 days agoHandshake completed112 ms
9 days agoHandshake completed185 ms
10 days agoHandshake completed56 ms
13 days agoHandshake completed45 ms
14 days agoHandshake completed49 ms
16 days agoHandshake completed262 ms
17 days agoHandshake completed44 ms
19 days agoHandshake completed38 ms
20 days agoHandshake completed50 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed49 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Crtsh and makes no claim about it beyond what these checks measured.