Skip to main content
Glama
natesilva

mcp-certificate-monitor

by natesilva
README.md
# MCP Certificate Monitor

Monitor SSL/TLS certificate expiry across your domains by asking Claude — no dashboards, no command-line tools.

## Prerequisites

- [uv](https://docs.astral.sh/uv/) installed
- [Claude Desktop](https://claude.ai/download) installed

## Setup

**1. Add the server to your Claude Desktop config**

Open the Claude Desktop configuration file:

- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`

Add the following:

```json
{
  "mcpServers": {
    "cert-monitor": {
      "command": "uvx",
      "args": ["mcp-certificate-monitor"]
    }
  }
}
```

`uvx` downloads and runs the package automatically — no cloning or installation step needed.

**2. Restart Claude Desktop**

After saving the config file, restart Claude Desktop. The server starts automatically when Claude needs it.

**3. Verify the connection**

Open a new conversation in Claude Desktop and ask:

> What certificate monitoring tools do you have available?

Claude should describe the tools exposed by this server (check certificate, add host, scan all, etc.).

## Alternative: run from source

If you prefer to run from a local clone:

```bash
git clone https://github.com/natesilva/mcp-certificate-monitor
cd mcp-certificate-monitor
```

Then use this config instead:

```json
{
  "mcpServers": {
    "cert-monitor": {
      "command": "uv",
      "args": ["run", "mcp-certificate-monitor"],
      "cwd": "/path/to/mcp-certificate-monitor"
    }
  }
}
```

## Documentation

- [What it does and example conversations](https://github.com/natesilva/mcp-certificate-monitor/blob/main/docs/overview.md)
- [Tool, resource & prompt reference](https://github.com/natesilva/mcp-certificate-monitor/blob/main/docs/reference.md)

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: adding a host, checking a certificate without state change, retrieving expiry reports, removing a host, and scanning all hosts. No overlap or confusion.

Naming Consistency4/5

Most tools follow the verb_noun pattern (add_monitored_host, check_certificate, get_expiry_report, remove_host), but 'scan_all' uses a verb_adverb pattern, causing a slight inconsistency.

Tool Count5/5

5 tools is well-scoped for a certificate monitoring service, covering all core operations without being excessive or insufficient.

Completeness4/5

The set covers add, remove, scan all, live check, and expiry reporting. Minor gap: no direct tool to retrieve stored data for a single host without a live check, but get_expiry_report returns all stored data, mitigating this.

Maintenance

ActivityInactive
ResponsivenessNo issues