# MCP Registry Validator — Check Endpoints Actually Resolve (remote · mcp-uptime.theopslog.workers.dev)

Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp-uptime.theopslog.workers.dev`: 58/100 (this document), [markdown](https://verifymcp.io/servers/operatorsheets-mcp-uptime/mcp-uptime.md), [page](https://verifymcp.io/servers/operatorsheets-mcp-uptime/mcp-uptime)

## Channel facts

- Endpoint: `https://mcp-uptime.theopslog.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## 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-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 311 tokens (~77/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http operatorsheets-mcp-uptime https://mcp-uptime.theopslog.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.operatorsheets-mcp-uptime]
url = "https://mcp-uptime.theopslog.workers.dev/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add operatorsheets-mcp-uptime --url https://mcp-uptime.theopslog.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  operatorsheets-mcp-uptime:
    url: "https://mcp-uptime.theopslog.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "operatorsheets-mcp-uptime": {
      "type": "http",
      "url": "https://mcp-uptime.theopslog.workers.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-08-03 (score 58, +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-08-02 (score 57, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-01 (score 57)

First indexed and scored.

## MCP tools (4)

### `check_mcp_endpoint` (~89 tokens)

Probe an MCP endpoint right now: is it alive, which transport it speaks, how many tools it exposes, and whether its tool schema changed since the last check. Use before depending on a third-party MCP server.

Input parameters:

- `include_tools` (boolean): Return the full tool list, not just the count.
- `url` (string, required): Public http(s) URL of the MCP endpoint to inspect.

### `get_uptime` (~70 tokens)

Uptime history for an MCP endpoint over the last N days (max 30), with incident windows. Reads stored history; does not probe.

Input parameters:

- `days` (integer): Window in days. Default 30.
- `url` (string, required): Public http(s) URL of the MCP endpoint to inspect.

### `get_known_tools` (~55 tokens)

The tool list last observed at an MCP endpoint, with the timestamp of the most recent schema change. Reads stored history; does not probe.

Input parameters:

- `url` (string, required): Public http(s) URL of the MCP endpoint to inspect.

### `check_schema_drift` (~70 tokens)

Probe an MCP endpoint and diff its tool schema against the last stored snapshot: tools added, removed, or whose description/inputSchema changed. Schema drift fails quietly mid-run, which is why it is worth checking.

Input parameters:

- `url` (string, required): Public http(s) URL of the MCP endpoint to inspect.

## Diagnostics

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

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 57

## Links

- Remote endpoint: https://mcp-uptime.theopslog.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/operatorsheets-mcp-uptime/mcp-uptime/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/operatorsheets-mcp-uptime/mcp-uptime/changelog.json
- HTML version of this page: https://verifymcp.io/servers/operatorsheets-mcp-uptime/mcp-uptime