# sitecheck (remote · 79-108-224-31.sslip.io)

Vet a domain (WHOIS age, DNS, SPF/DMARC, TLS) or read a web page as Markdown. Run by an AI agent.

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

## Components

- remote · `79-108-224-31.sslip.io`: 68/100 (this document), [markdown](https://verifymcp.io/servers/io-sslip-79-108-224-31-sitecheck/79-108-224-31.md), [page](https://verifymcp.io/servers/io-sslip-79-108-224-31-sitecheck/79-108-224-31)

## Channel facts

- Endpoint: `https://79-108-224-31.sslip.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-10-18.

- **Endpoint Security**: 57/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 8 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.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 829 tokens (~103/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 sitecheck MCP server?

sitecheck is a hosted endpoint at https://79-108-224-31.sslip.io/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 io-sslip-79-108-224-31-sitecheck 'https://79-108-224-31.sslip.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-sslip-79-108-224-31-sitecheck": {
      "url": "https://79-108-224-31.sslip.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-sslip-79-108-224-31-sitecheck": {
      "type": "http",
      "url": "https://79-108-224-31.sslip.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-sslip-79-108-224-31-sitecheck]
url = "https://79-108-224-31.sslip.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-sslip-79-108-224-31-sitecheck": {
      "type": "remote",
      "url": "https://79-108-224-31.sslip.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-sslip-79-108-224-31-sitecheck --url 'https://79-108-224-31.sslip.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-sslip-79-108-224-31-sitecheck:
    url: "https://79-108-224-31.sslip.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-sslip-79-108-224-31-sitecheck": {
      "Transport": "http",
      "Url": "https://79-108-224-31.sslip.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-sslip-79-108-224-31-sitecheck -t streamable-http -u 'https://79-108-224-31.sslip.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-sslip-79-108-224-31-sitecheck": {
      "type": "http",
      "url": "https://79-108-224-31.sslip.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-10-17 (score 68, +1)

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

### 2026-10-15 (score 67, +1)

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

### 2026-10-13 (score 66, +1)

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

### 2026-10-10 (score 65, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-08 (score 64)

First indexed and scored.

## MCP tools (8)

### `check_domain` (~135 tokens)

Is this domain what it claims to be? One call returns registration age and registrar (RDAP), DNS records, SPF and DMARC, TLS certificate health and expiry, the HTTP redirect chain, security headers, and a list of plain-language findings. Use it to vet a merchant, sender or link before trusting it. Live lookups, no API key. 5 free calls per day across all tools; pass `key` to use a prepaid balance (0.01 USDC per call).

Input parameters:

- `domain` (string, required): Public hostname, for example example.com
- `key` (string): Optional API key from create_key

### `read_url` (~191 tokens)

Fetch a public web page and get its main content as clean Markdown: title, description, language, publish date and the article text with headings, lists, tables, code blocks and links, without navigation, ads or scripts. Built for LLM agents that need to read a URL. Respects robots.txt; static HTML only (no JavaScript rendering). Not charged if the page cannot be read. 5 free calls per day across all tools; pass `key` to use a prepaid balance (0.005 USDC per call).

Input parameters:

- `key` (string): Optional API key from create_key
- `links` (string): Set to 0 to drop link targets and keep only the link text
- `max_chars` (integer): Maximum characters of content to return (default 20000, maximum 100000)
- `url` (string, required): Absolute http(s) URL of the page to read

### `email_auth` (~137 tokens)

Can mail from this domain be spoofed? Returns MX, the SPF record and how strict it is, the DMARC policy, DKIM keys found under common selectors, MTA-STS, TLS-RPT and BIMI, with a spoofable verdict and findings. Use it to judge a sender's domain or audit your own before sending. Live DNS lookups. 5 free calls per day across all tools; pass `key` to use a prepaid balance (0.005 USDC per call).

Input parameters:

- `domain` (string, required): Public hostname, for example example.com
- `key` (string): Optional API key from create_key

### `tls_certificate` (~112 tokens)

Live TLS handshake with a host on port 443: whether the certificate is trusted, who issued it, the names it covers, the protocol version, the expiry date and days left. Use it to catch an expiring or misissued certificate. 5 free calls per day across all tools; pass `key` to use a prepaid balance (0.005 USDC per call).

Input parameters:

- `domain` (string, required): Public hostname, for example example.com
- `key` (string): Optional API key from create_key

### `domain_registration` (~120 tokens)

Structured registration data for a domain from RDAP, the successor to WHOIS: registrar, creation, expiry and last-changed dates, age in days, status flags, nameservers and whether DNSSEC is signed. Use it to spot a newly registered or soon-to-expire domain. 5 free calls per day across all tools; pass `key` to use a prepaid balance (0.005 USDC per call).

Input parameters:

- `domain` (string, required): Public hostname, for example example.com
- `key` (string): Optional API key from create_key

### `create_key` (~31 tokens)

Create an API key and get instructions for funding it with USDC on Base. Only needed beyond the free limit.

### `claim_deposit` (~46 tokens)

Credit a key after sending USDC on Base. The amount's last four decimals must be the key's tag.

Input parameters:

- `tx` (string, required): Transaction hash of the USDC transfer

### `balance` (~23 tokens)

Remaining balance of an API key.

Input parameters:

- `key` (string, required): API key

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-sslip-79-108-224-31-sitecheck/79-108-224-31#diagnostics

## Score history

- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 66
- 2026-10-13: 66
- 2026-10-12: 65
- 2026-10-10: 65
- 2026-10-08: 64

## Common questions

### What is the sitecheck MCP server?

sitecheck is an MCP server listed in the public MCP registry as io.sslip.79-108-224-31/sitecheck. Vet a domain (WHOIS age, DNS, SPF/DMARC, TLS) or read a web page as Markdown. Run by an AI agent. This page covers its hosted endpoint (https://79-108-224-31.sslip.io/mcp).

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

sitecheck scores 68 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 sitecheck MCP server expose?

sitecheck exposes 8 tools: check_domain, read_url, email_auth, tls_certificate, domain_registration, and 3 more. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.

### Does the sitecheck MCP server require authentication?

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

### Is the sitecheck MCP server still maintained?

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

## Links

- Remote endpoint: https://79-108-224-31.sslip.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-sslip-79-108-224-31-sitecheck/79-108-224-31.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-sslip-79-108-224-31-sitecheck/79-108-224-31.json
- HTML version of this page: https://verifymcp.io/servers/io-sslip-79-108-224-31-sitecheck/79-108-224-31