Remote MCP · Endpoint

Boring Utils Expiry Watch MCP server

No. Boring Utils Expiry Watch answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://boringutils.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.hal-boring-utils/expiry-watch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
702 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check a site's TLS certificate and its domain registration expiry. Read-only, no sign-in.
Listing
From the official MCP registry (active).
Recent checks of Boring Utils Expiry Watch
CheckedResultHandshake
8 hours agoHandshake completed702 ms
10 days agoHandshake completed95 ms
11 days agoHandshake completed140 ms
11 days agoHandshake completed127 ms
13 days agoHandshake completed82 ms
15 days agoHandshake completed113 ms
15 days agoHandshake completed85 ms
16 days agoHandshake completed271 ms
17 days agoHandshake completed107 ms
19 days agoHandshake completed109 ms
22 days agoHandshake completed573 ms
24 days agoHandshake completed71 ms
26 days agoHandshake completed116 ms

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

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 Boring Utils Expiry Watch and makes no claim about it beyond what these checks measured.