# Boring Utils Expiry Watch (remote · boringutils.com)

Check a site's TLS certificate and its domain registration expiry. Read-only, no sign-in.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `boringutils.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/hal-boring-utils-expiry-watch/api-mcp.md), [page](https://verifymcp.io/servers/hal-boring-utils-expiry-watch/api-mcp)

## Channel facts

- Endpoint: `https://boringutils.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 273 tokens (~136/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Boring Utils Expiry Watch MCP server?

Boring Utils Expiry Watch is a hosted endpoint at https://boringutils.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http hal-boring-utils-expiry-watch 'https://boringutils.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "hal-boring-utils-expiry-watch": {
      "url": "https://boringutils.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hal-boring-utils-expiry-watch": {
      "type": "http",
      "url": "https://boringutils.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.hal-boring-utils-expiry-watch]
url = "https://boringutils.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hal-boring-utils-expiry-watch": {
      "type": "remote",
      "url": "https://boringutils.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hal-boring-utils-expiry-watch --url 'https://boringutils.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  hal-boring-utils-expiry-watch:
    url: "https://boringutils.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "hal-boring-utils-expiry-watch": {
      "Transport": "http",
      "Url": "https://boringutils.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add hal-boring-utils-expiry-watch -t streamable-http -u 'https://boringutils.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "hal-boring-utils-expiry-watch": {
      "type": "http",
      "url": "https://boringutils.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 73, 0)

- [security] Tool “check_certificate” rewrote its description, which is the text the model reads
- [security] Tool “check_domain_expiry” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 98 → 136

### 2026-10-24 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (2)

### `check_certificate` (~130 tokens)

Check a TLS certificate

Connects to a domain on port 443 and reports its TLS certificate: whether it is trusted and matches the name, the issuer, the expiry date and days left, the lifetime, the chain and the TLS version, what each of its server addresses serves (up to 4 IPv4 and 4 IPv6), and, for certificates from Let’s Encrypt, Google Trust Services, ZeroSSL or Sectigo, the renewal window the CA suggests (ACME Renewal Information).

Input parameters:

- `domain` (string, required): A public domain name, like example.com. A URL also works: only its host name is used.

### `check_domain_expiry` (~100 tokens)

Check a domain registration expiry

Looks up a domain registration over RDAP at the registry for its TLD: when it expires, the registrar, the statuses (flagging a hold, redemption, pending delete or pending transfer) and the nameservers. Subdomains are looked up by their registered domain (www.example.co.uk becomes example.co.uk).

Input parameters:

- `domain` (string, required): A public domain name, like example.com. A URL also works: only its host name is used.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/hal-boring-utils-expiry-watch/api-mcp#diagnostics

## Score history

- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71

## Common questions

### What is the Boring Utils Expiry Watch MCP server?

Boring Utils Expiry Watch is an MCP server listed in the public MCP registry as io.github.hal-boring-utils/expiry-watch. Check a site's TLS certificate and its domain registration expiry. Read-only, no sign-in. This page covers its hosted endpoint (https://boringutils.com/api/mcp).

### Is the Boring Utils Expiry Watch MCP server safe to use?

Boring Utils Expiry Watch scores 78 out of 100 on VerifyMCP. 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 Boring Utils Expiry Watch MCP server expose?

Boring Utils Expiry Watch exposes 2 tools: check_certificate, check_domain_expiry. Their descriptions and schemas cost roughly 230 tokens of context every time the server is loaded.

### Does the Boring Utils Expiry Watch MCP server require authentication?

No. We connected to Boring Utils Expiry Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Boring Utils Expiry Watch MCP server still maintained?

Boring Utils Expiry Watch is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://boringutils.com/api/mcp
- Website: https://boringutils.com/expiry-watch
- Changelog RSS feed: https://verifymcp.io/servers/hal-boring-utils-expiry-watch/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/hal-boring-utils-expiry-watch/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/hal-boring-utils-expiry-watch/api-mcp