Remote MCP · Endpoint

TLS Radar MCP server

No. TLS Radar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tlsradar.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.tlsradar/tlsradar
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
73 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
SSL/TLS scanning, free Let's Encrypt issuance, and certificate-expiry monitoring.
Listing
From the official MCP registry (active).
Recent checks of TLS Radar
CheckedResultHandshake
1 hour agoHandshake completed73 ms
2 days agoHandshake completed105 ms
4 days agoHandshake completed68 ms
5 days agoHandshake completed114 ms
7 days agoHandshake completed72 ms
8 days agoHandshake completed593 ms
9 days agoHandshake completed83 ms
12 days agoHandshake completed47 ms
13 days agoHandshake completed153 ms
15 days agoHandshake completed68 ms
16 days agoHandshake completed107 ms
18 days agoHandshake completed66 ms
19 days agoHandshake completed61 ms
20 days agoHandshake completed76 ms
20 days agoHandshake completed573 ms
21 days agoHandshake completed52 ms
22 days agoHandshake completed157 ms

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

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 TLS Radar and makes no claim about it beyond what these checks measured.