Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+3 this week 68 Trust /100

Last scanned (15 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 829 tokens (~103/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +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.

  • 15 Oct 26 +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.

  • 13 Oct 26 +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.

  • 10 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 8 Oct 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 18 Oct 2026 · Probed https://79-108-224-31.sslip.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=79-108-224-31.sslip.io CN=YE2,O=Let's Encrypt,C=US 7 Oct 2026 5 Jan 2027 ECDSA 256 ECDSA-SHA384 549ae68a95e8384e3d82d784265c9a69575
SANs: 79-108-224-31.sslip.io
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of 79-108-224-31.sslip.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
sslip.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://79-108-224-31.sslip.io/mcp Verified 200
http (plaintext) http://79-108-224-31.sslip.io/mcp HTTPS enforced 308 https://79-108-224-31.sslip.io/mcp
MCP tools · 8 exposed · ~795 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
balance ~23

Remaining balance of an API key.

NameTypeReqDescription
keystringyesAPI key

No output schema declared.

No examples provided.

check_domain ~135

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).

NameTypeReqDescription
domainstringyesPublic hostname, for example example.com
keystring–Optional API key from create_key

No output schema declared.

No examples provided.

claim_deposit ~46

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

NameTypeReqDescription
txstringyesTransaction hash of the USDC transfer

No output schema declared.

No examples provided.

create_key ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

domain_registration ~120

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).

NameTypeReqDescription
domainstringyesPublic hostname, for example example.com
keystring–Optional API key from create_key

No output schema declared.

No examples provided.

email_auth ~137

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).

NameTypeReqDescription
domainstringyesPublic hostname, for example example.com
keystring–Optional API key from create_key

No output schema declared.

No examples provided.

read_url ~191

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).

NameTypeReqDescription
keystring–Optional API key from create_key
linksstring–Set to 0 to drop link targets and keep only the link text
max_charsinteger–Maximum characters of content to return (default 20000, maximum 100000)
urlstringyesAbsolute http(s) URL of the page to read

No output schema declared.

No examples provided.

tls_certificate ~112

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).

NameTypeReqDescription
domainstringyesPublic hostname, for example example.com
keystring–Optional API key from create_key

No output schema declared.

No examples provided.

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.

remote · 79-108-224-31.sslip.io

# add to Claude Code
claude mcp add --transport http io-sslip-79-108-224-31-sitecheck 'https://79-108-224-31.sslip.io/mcp'
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.