# SteadySite (remote · steadysite.dev)

Check SSL certificate and domain expiry for any site, see plans, and get a monitoring sign-up link.

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

## Components

- remote · `steadysite.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite.md), [page](https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite)

## Channel facts

- Endpoint: `https://steadysite.dev/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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 362 tokens (~120/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 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.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 SteadySite MCP server?

SteadySite is a hosted endpoint at https://steadysite.dev/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 dev-steadysite-steadysite 'https://steadysite.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-steadysite-steadysite": {
      "url": "https://steadysite.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-steadysite-steadysite": {
      "type": "http",
      "url": "https://steadysite.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-steadysite-steadysite]
url = "https://steadysite.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-steadysite-steadysite": {
      "type": "remote",
      "url": "https://steadysite.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-steadysite-steadysite --url 'https://steadysite.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-steadysite-steadysite:
    url: "https://steadysite.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-steadysite-steadysite": {
      "Transport": "http",
      "Url": "https://steadysite.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-steadysite-steadysite -t streamable-http -u 'https://steadysite.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-steadysite-steadysite": {
      "type": "http",
      "url": "https://steadysite.dev/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-20 (score 73, +1)

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

### 2026-11-17 (score 72, +1)

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

### 2026-11-15 (score 71, +1)

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

### 2026-11-13 (score 70, +1)

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

### 2026-11-11 (score 69, +1)

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

### 2026-11-10 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 68)

First indexed and scored.

## MCP tools (3)

### `check_ssl_domain_expiry` (~130 tokens)

Check SSL certificate & domain expiry

Look up a website's SSL certificate expiry (date, days left, issuer), domain registration expiry (date, days left, registrar) and current HTTP status. Use when someone asks when a site's certificate or domain expires, who issued it, or whether the site is up. "warn" means expiring within 30 days, "bad" means expired or down. Results are cached for 15 minutes; fresh lookups are limited to 15 per 10 minutes.

Input parameters:

- `domain` (string, required): Hostname or URL, e.g. example.com or https://www.example.com/page

Output parameters:

- `checked_at` (string)
- `domain` (string)
- `domain_registration` (object)
- `host` (string)
- `http` (object)
- `monitor_url` (string): Link to start monitoring this domain with email alerts.
- `ssl` (object)

### `get_plans` (~66 tokens)

Get SteadySite plans and pricing

Return SteadySite plans (Free, Pro, Agency): monthly price in USD, monitors, check interval, client groups with their own branded reports and status pages, white-label, and whether paid checkout is open. Use when someone asks what SteadySite costs or which plan fits.

### `start_monitoring` (~97 tokens)

Get a link to start monitoring a domain

Return a sign-up link that starts SteadySite monitoring (uptime, SSL expiry and domain expiry email alerts, monthly client report) for a domain. The person opens the link, signs in with their email (free plan, no credit card) and the domain is pre-filled. Nothing is created until they confirm.

Input parameters:

- `domain` (string, required): Hostname or URL, e.g. example.com or https://www.example.com/page

Output parameters:

- `domain` (string)
- `note` (string)
- `plan` (string)
- `signup_url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 73
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 72
- 2026-11-16: 71
- 2026-11-15: 71
- 2026-11-14: 70
- 2026-11-13: 70
- 2026-11-12: 69
- 2026-11-11: 69
- 2026-11-10: 68
- 2026-11-09: 68

## Common questions

### What is the SteadySite MCP server?

SteadySite is an MCP server listed in the public MCP registry as dev.steadysite/steadysite. Check SSL certificate and domain expiry for any site, see plans, and get a monitoring sign-up link. This page covers its hosted endpoint (https://steadysite.dev/mcp).

### Is the SteadySite MCP server safe to use?

SteadySite scores 73 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 SteadySite MCP server expose?

SteadySite exposes 3 tools: check_ssl_domain_expiry, get_plans, start_monitoring. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.

### Does the SteadySite MCP server require authentication?

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

### Is the SteadySite MCP server still maintained?

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

### What did VerifyMCP test on the SteadySite MCP server?

VerifyMCP ran 12 checks on SteadySite, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about SteadySite: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://steadysite.dev/mcp
- Website: https://steadysite.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite.json
- HTML version of this page: https://verifymcp.io/servers/dev-steadysite-steadysite/steadysite
