A FastMCP server that lets an AI host monitor certificate expiry across a set of domains
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-certificate-monitor","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 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)
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.