# Uptimeify (remote · uptimeify.io)

Free anonymous website, DNS, email and TLS checks, plus read-only access to your monitors.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-06

## Components

- remote · `uptimeify.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-uptimeify-mcp-server/uptimeify.md), [page](https://verifymcp.io/servers/io-uptimeify-mcp-server/uptimeify)

## Channel facts

- Endpoint: `https://uptimeify.io/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-08-06.

- **Endpoint Security**: 66/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 25 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **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 1109 tokens (~44/item across 25 items; 25 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-uptimeify-mcp-server https://uptimeify.io/mcp
```

### Codex

```toml
[mcp_servers.io-uptimeify-mcp-server]
url = "https://uptimeify.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-uptimeify-mcp-server --url https://uptimeify.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-uptimeify-mcp-server:
    url: "https://uptimeify.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-uptimeify-mcp-server": {
      "type": "http",
      "url": "https://uptimeify.io/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-06 (score 68, +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-05 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “asn_lookup” now declares an output schema
- [functional improvement] Tool “check_dns” now declares an output schema
- [functional improvement] Tool “check_history” now declares an output schema
- [functional improvement] Tool “check_ssl” now declares an output schema
- [functional improvement] Tool “dkim_check” now declares an output schema
- [functional improvement] Tool “dmarc_check” now declares an output schema
- [functional improvement] Tool “dns_propagation” now declares an output schema
- [functional improvement] Tool “dnsbl_check” now declares an output schema
- [functional improvement] Tool “domain_expiry” now declares an output schema
- [functional improvement] Tool “hsts_check” now declares an output schema
- [functional improvement] Tool “http_headers” now declares an output schema
- [functional improvement] Tool “ip_geolocation” now declares an output schema
- [functional improvement] Tool “list_monitors” now declares an output schema
- [functional improvement] Tool “monitor_status” now declares an output schema
- [functional improvement] Tool “mx_lookup” now declares an output schema
- [functional improvement] Tool “ping_test” now declares an output schema
- [functional improvement] Tool “port_check” now declares an output schema
- [functional improvement] Tool “redirect_check” now declares an output schema
- [functional improvement] Tool “response_time” now declares an output schema
- [functional improvement] Tool “reverse_dns” now declares an output schema
- [functional improvement] Tool “spf_check” now declares an output schema
- [functional improvement] Tool “uptime_summary” now declares an output schema
- [functional improvement] Tool “website_status” now declares an output schema
- [functional improvement] Tool “whois” now declares an output schema
- [functional improvement] Tool “list_incidents” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-08-04 (score 67)

First indexed and scored.

## MCP tools (25)

### `check_ssl` (~63 tokens)

Check a host's TLS/SSL certificate: issuer, validity dates, expiry, chain and trust verdict.

Input parameters:

- `host` (string, required): Domain name (not an IP), e.g. deinkunde.com
- `port` (integer): TLS port, default 443

Output parameters:

- `authorizationError`
- `daysUntilExpiry`
- `expired`
- `fingerprint256`
- `found`
- `host`
- `hostnameMatch`
- `ip`
- `issuerCN`
- `issuerO`
- `notYetValid`
- `ok`
- `port`
- `san`
- `selfSigned`
- `serialNumber`
- `subjectCN`
- `trusted`
- `validFrom`
- `validTo`

### `check_dns` (~44 tokens)

Check a domain's DNS records (A/AAAA/CNAME/TXT/NS and more).

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `domain`
- `found`
- `ok`
- `records`
- `warnings`

### `dns_propagation` (~39 tokens)

Check DNS propagation of a domain across multiple public resolvers.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `consistent`
- `domain`
- `ok`
- `results`
- `type`

### `mx_lookup` (~39 tokens)

MX lookup for a domain: its mail exchanger records and their addresses.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `domain`
- `found`
- `ok`
- `servers`

### `spf_check` (~40 tokens)

Check a domain's SPF record: fetch it and evaluate the policy.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `all`
- `domain`
- `error`
- `found`
- `lookups`
- `ok`
- `record`
- `terms`
- `warnings`

### `dkim_check` (~62 tokens)

Check a domain's DKIM public key for a given selector: fetch it and validate it.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com
- `selector` (string, required): DKIM selector, e.g. google or default

Output parameters:

- `bits`
- `domain`
- `error`
- `found`
- `hasKey`
- `keyType`
- `ok`
- `record`
- `selector`
- `tags`
- `warnings`

### `dmarc_check` (~43 tokens)

Check a domain's DMARC policy record: fetch it and evaluate the policy.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `domain`
- `error`
- `found`
- `ok`
- `pct`
- `policy`
- `record`
- `subPolicy`
- `tags`
- `warnings`

### `dnsbl_check` (~40 tokens)

DNSBL check: whether a public IP address is listed on common DNS blacklists.

Input parameters:

- `ip` (string, required): Public IPv4 or IPv6 address

Output parameters:

- `clean`
- `ip`
- `listedCount`
- `ok`
- `results`
- `total`

### `whois` (~34 tokens)

Retrieve WHOIS registration data for a domain.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `contacts`
- `createdAt`
- `domain`
- `error`
- `expiresAt`
- `found`
- `nameservers`
- `ok`
- `registrar`
- `statuses`
- `tld`
- `tldSupported`
- `updatedAt`

### `domain_expiry` (~38 tokens)

Check a domain's registration expiry date and the days remaining.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `createdAt`
- `daysUntilExpiry`
- `domain`
- `error`
- `expiresAt`
- `found`
- `ok`
- `registrar`
- `statuses`
- `tld`
- `tldSupported`
- `updatedAt`

### `http_headers` (~36 tokens)

Fetch the HTTP response headers for a URL.

Input parameters:

- `url` (string, required): Full URL, e.g. https://deinkunde.com

Output parameters:

- `headers`
- `ok`
- `redirects`
- `status`
- `statusText`
- `url`

### `hsts_check` (~39 tokens)

HSTS check: a domain's HTTP Strict Transport Security configuration.

Input parameters:

- `domain` (string, required): Domain name, e.g. deinkunde.com

Output parameters:

- `domain`
- `httpsRedirect`
- `includeSubDomains`
- `maxAge`
- `ok`
- `preload`
- `preloadReady`
- `present`
- `raw`
- `warnings`

### `redirect_check` (~43 tokens)

Check the HTTP redirect chain for a URL, tracing it to the final destination.

Input parameters:

- `url` (string, required): Full URL, e.g. https://deinkunde.com

Output parameters:

- `finalStatus`
- `finalStatusText`
- `finalUrl`
- `hops`
- `ok`
- `start`
- `totalHops`
- `warnings`

### `port_check` (~41 tokens)

Check whether a TCP port is open on a host.

Input parameters:

- `host` (string, required): Domain name or host
- `port` (integer, required): TCP port to test

Output parameters:

- `host`
- `ip`
- `ok`
- `port`
- `state`
- `timeMs`

### `ping_test` (~46 tokens)

Ping test: measure TCP reachability and round-trip time to a host.

Input parameters:

- `host` (string, required): Domain name or host
- `port` (integer): Port, default 443

Output parameters:

- `attempts`
- `avgMs`
- `host`
- `ip`
- `lossPct`
- `maxMs`
- `minMs`
- `ok`
- `port`
- `received`
- `sent`

### `website_status` (~41 tokens)

Check whether a website is up, its HTTP status and response timing.

Input parameters:

- `url` (string, required): Full URL, e.g. https://deinkunde.com

Output parameters:

- `ok`
- `redirects`
- `responseTimeMs`
- `server`
- `status`
- `statusText`
- `up`
- `url`

### `response_time` (~44 tokens)

Measure a website's response time (DNS, connect, TTFB, total).

Input parameters:

- `url` (string, required): Full URL, e.g. https://deinkunde.com

Output parameters:

- `avg`
- `max`
- `min`
- `ok`
- `samples`
- `status`
- `up`
- `url`

### `ip_geolocation` (~42 tokens)

IP geolocation for a public IP address or a domain (country, region, ASN, org).

Input parameters:

- `query` (string, required): Public IP address or domain name

Output parameters:

- `asns`
- `cc`
- `found`
- `ip`
- `ok`
- `prefix`
- `ptr`
- `query`
- `registry`
- `resolvedFromDomain`

### `asn_lookup` (~39 tokens)

ASN lookup for a public IP or domain: the autonomous system and its network owner.

Input parameters:

- `query` (string, required): Public IP address or domain name

Output parameters:

- `asns`
- `cc`
- `found`
- `ip`
- `ok`
- `prefix`
- `query`
- `registry`

### `reverse_dns` (~35 tokens)

Reverse DNS: resolve a public IP address to its PTR hostname.

Input parameters:

- `ip` (string, required): Public IPv4 or IPv6 address

Output parameters:

- `error`
- `hostnames`
- `ip`
- `ok`

### `list_monitors` (~40 tokens)

List the website monitors the caller's API token can see (customer token: its own customer; organization token: all customers in the org). Read-only.

Output parameters:

- `items`
- `page`
- `perPage`
- `total`

### `monitor_status` (~45 tokens)

Get a single website monitor by id, including its current up/down status and configuration.

Input parameters:

- `monitor_id` (string, required): The monitor/website id (public id from list_monitors)

Output parameters:

- `avgResponseDay`
- `avgResponseMonth`
- `avgResponseYear`
- `createdAt`
- `hasCritical`
- `hasWarning`
- `id`
- `isActive`
- `isDown`
- `isRecovering`
- `monitoringType`
- `name`
- `publicId`
- `upSinceAt`
- `updatedAt`
- `uptimeDay`
- `uptimeMonth`
- `uptimeYear`
- `url`

### `list_incidents` (~43 tokens)

List recent incidents across all of the caller's monitors (most recent first).

Input parameters:

- `limit` (integer): Max incidents to return, default 100, max 500

Output parameters:

- `incidents`

### `check_history` (~86 tokens)

Get the recent check history for a website monitor. Optionally bound by an ISO date range.

Input parameters:

- `from` (string): ISO date/time lower bound, e.g. 2026-07-01
- `monitor_id` (string, required): The monitor/website id
- `to` (string): ISO date/time upper bound, e.g. 2026-07-23

Output parameters:

- `data`
- `page`
- `pageCount`
- `total`

### `uptime_summary` (~47 tokens)

Get uptime and average response-time summary (day / month / year) for a website monitor.

Input parameters:

- `monitor_id` (string, required): The monitor/website id (public id from list_monitors)

Output parameters:

- `day`
- `dayAvgResponse`
- `month`
- `monthAvgResponse`
- `year`
- `yearAvgResponse`

## Diagnostics

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

## Score history

- 2026-08-06: 68
- 2026-08-05: 67
- 2026-08-04: 67

## Links

- Remote endpoint: https://uptimeify.io/mcp
- Website: https://uptimeify.io/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/io-uptimeify-mcp-server/uptimeify.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-uptimeify-mcp-server/uptimeify.json
- HTML version of this page: https://verifymcp.io/servers/io-uptimeify-mcp-server/uptimeify