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.

Uptimeify

REMOTE · UPTIMEIFY.IO

Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.

Available components

0 this week 89 Trust /100

Last scanned (20 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2255 tokens (~112/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 12 Nov 26 0
    • Judged manipulation: unverified → pass ▲ security
    • Tool “dnsbl_check” rewrote its description, which is the text the model reads security
    • Tool “port_check” rewrote its description, which is the text the model reads security
    • Server version: 1.14.0 → 1.15.0 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Server version: 1.12.0 → 1.14.0 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 0
    • Server version: 1.11.1 → 1.12.0 functional
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 21 Nov 2026 · Probed https://uptimeify.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=uptimeify.io CN=YE1,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA384 64596f6ae71a0535b3db0f5931960ea067a
SANs: uptimeify.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 secure

Validation of uptimeify.io. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
uptimeify.io. DS published 62480 13 Verified
uptimeify.io. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.googletagmanager.com https://*.google-analytics.com https://*.lfeeder.com https://cal.uptimeify.io; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://uptimeify.b-cdn.net https://ui-avatars.com https://images.unsplash.com https://i.pravatar.cc https://*.google-analytics.com https://*.googletagmanager.com https://*.lfeeder.com; font-src 'self' data:; connect-src 'self' https://*.googletagmanager.com https://*.google-analytics.com https://*.lfeeder.com https://cal.uptimeify.io https://*.sentry.io https://*.ingest.sentry.io; frame-src 'self' https://cal.uptimeify.io; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; report-uri /api/csp-report; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://uptimeify.io/mcp Verified 200
http (plaintext) http://uptimeify.io/mcp HTTPS enforced 308 https://uptimeify.io/mcp
MCP tools · 20 exposed · ~2,255 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
asn_lookup ~107

Resolves a public IP address, or a domain, to the autonomous system that announces it: AS number and name, announced prefix, country code, registry and allocation date. Distinguishes hosting providers, CDNs and corporate networks; it does not identify the site owner. Private and reserved addresses have no announcing AS. ip_geolocation returns the same AS data plus country and PTR. Anonymous, rate-limited per IP.

NameTypeReqDescription
querystringyesPublic IP address or domain name
NameTypeReqDescription
asns–––
ccstring|null––
foundboolean|null––
ipstring|null––
okboolean|null––
prefixstring|null––
querystring|null––
registrystring|null––

No examples provided.

check_dns ~106

Resolves a domain's DNS records in one call (A, AAAA, CNAME, MX, TXT, NS, SOA and more) and returns each record type with its values, or a per-type error where a lookup failed. Answers come from a single resolver; dns_propagation compares several. Reads records only and never connects to the host. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
domainstring|null––
foundboolean|null––
okboolean|null––
records–––
warnings–––

No examples provided.

check_ssl ~146

Fetches and evaluates a host's TLS certificate over a live handshake: subject, issuer, validity window, days until expiry, hostname match, chain trust, self-signed and expired flags, SANs, serial and SHA-256 fingerprint. Takes a hostname (not an IP address) and an optional port (default 443). A single sample taken now; HTTP behaviour is covered by website_status and the HSTS policy by hsts_check. Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
hoststringyesDomain name (not an IP), e.g. deinkunde.com
portinteger–TLS port, default 443
NameTypeReqDescription
authorizationErrorstring|null––
daysUntilExpirynumber|null––
expiredboolean|null––
fingerprint256string|null––
foundboolean|null––
hoststring|null––
hostnameMatchboolean|null––
ipstring|null––
issuerCNstring|null––
issuerOstring|null––
notYetValidboolean|null––
okboolean|null––
portnumber|null––
san–––
selfSignedboolean|null––
serialNumberstring|null––
subjectCNstring|null––
trustedboolean|null––
validFromstring|null––
validTostring|null––

No examples provided.

dkim_check ~134

Fetches and validates the DKIM public key at <selector>._domainkey.<domain>: parsed tags, key type, key size and warnings such as a revoked or malformed key. The selector is required and cannot be derived from the domain; it appears in a message's DKIM-Signature header (common provider values: google, selector1, default, k1). An unused selector returns found=false. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
selectorstringyesDKIM selector, e.g. google or default
NameTypeReqDescription
bitsnumber|null––
domainstring|null––
errorstring|null––
foundboolean|null––
hasKeyboolean|null––
keyTypestring|null––
okboolean|null––
recordstring|null––
selectorstring|null––
tags–––
warnings–––

No examples provided.

dmarc_check ~113

Fetches a domain's DMARC record from _dmarc.<domain> and evaluates it: raw record, parsed tags, policy and subdomain policy, percentage, and warnings for records that parse but offer no protection (p=none, missing rua). Reports the published policy, not whether real mail passes it; spf_check and dkim_check cover the mechanisms it aligns against. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
domainstring|null––
errorstring|null––
foundboolean|null––
okboolean|null––
pctnumber|null––
policystring|null––
recordstring|null––
subPolicystring|null––
tags–––
warnings–––

No examples provided.

dns_propagation ~95

Queries one domain against several public resolvers and compares the answers, which tells a recent record change apart from a stale cache. Returns each resolver with its values and a `consistent` flag that stays false while the answers differ. check_dns is the cheaper call for a single reading of all record types. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
consistentboolean|null––
domainstring|null––
okboolean|null––
results–––
typestring|null––

No examples provided.

dnsbl_check ~138

Checks a public IP address against common DNS blocklists and returns, per list, whether it is listed, the list's reason code and delisting URL, plus totals and a `clean` flag. Takes an IP address, not a domain (mx_lookup or check_dns resolve one). Slow lists are skipped rather than awaited, so partial=true marks a provisional verdict; lists that could not answer are counted in `zonesFailed` and keep `clean` false. One call reflects only the current moment. Anonymous, with the strictest per-IP rate limit of the anonymous tools.

NameTypeReqDescription
ipstringyesPublic IPv4 or IPv6 address
NameTypeReqDescription
cleanboolean|null––
ipstring|null––
listedCountnumber|null––
okboolean|null––
partialboolean|null––
results–––
totalnumber|null––
zonesFailednumber|null––
zonesQueriednumber|null––

No examples provided.

domain_expiry ~104

Reports a domain's registration expiry from WHOIS with the remaining days, plus registrar, creation and update dates and the EPP status codes that reveal redemption or pending delete. Covers the registration, not the TLS certificate (check_ssl). tldSupported=false means the TLD has no queryable WHOIS server, not that the domain is unregistered. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
createdAtstring|null––
daysUntilExpirynumber|null––
domainstring|null––
errorstring|null––
expiresAtstring|null––
foundboolean|null––
okboolean|null––
registrarstring|null––
statuses–––
tldstring|null––
tldSupportedboolean|null––
updatedAtstring|null––

No examples provided.

hsts_check ~102

Checks a domain's HTTP Strict Transport Security setup: header presence and raw value, max-age, includeSubDomains and preload flags, whether plain HTTP redirects to HTTPS, preload-list eligibility, and warnings for ineffective values. Reports the advertised policy only; the certificate is check_ssl and the redirect chain redirect_check. Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
domainstring|null––
httpsRedirectboolean|null––
includeSubDomainsboolean|null––
maxAgenumber|null––
okboolean|null––
preloadboolean|null––
preloadReadyboolean|null––
presentboolean|null––
rawstring|null––
warnings–––

No examples provided.

http_headers ~92

Fetches a URL and returns its HTTP response headers verbatim as a name/value map, with the status line and every redirect hop. The response body is never returned. website_status gives a plain up/down verdict and redirect_check the redirect chain alone. Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
urlstringyesFull URL, e.g. https://deinkunde.com
NameTypeReqDescription
headers–––
okboolean|null––
redirects–––
statusnumber|null––
statusTextstring|null––
urlstring|null––

No examples provided.

ip_geolocation ~105

Locates a public IP address, or a domain resolved to one, at network level: country code, registry, announced prefix, PTR hostname and autonomous systems. Registry-based, so it names the network operator's country, which for hosted or CDN addresses differs from where a visitor or business is located; it is not a street address. Private and reserved addresses have no answer. Anonymous, rate-limited per IP.

NameTypeReqDescription
querystringyesPublic IP address or domain name
NameTypeReqDescription
asns–––
ccstring|null––
foundboolean|null––
ipstring|null––
okboolean|null––
prefixstring|null––
ptrstring|null––
querystring|null––
registrystring|null––
resolvedFromDomainboolean|null––

No examples provided.

mx_lookup ~105

Looks up a domain's MX records and resolves each mail exchanger to its IPv4 and IPv6 addresses, ordered by priority, flagging hosts that resolve into private address space. Shows where mail is delivered; it does not connect to the servers or test SMTP, and sender authorisation is covered by spf_check, dkim_check and dmarc_check. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
domainstring|null––
foundboolean|null––
okboolean|null––
servers–––

No examples provided.

ping_test ~114

Measures reachability and round-trip time with repeated TCP connections to a host port (default 443), returning every attempt, sent and received counts, packet loss and min/avg/max milliseconds. A TCP handshake, not an ICMP echo, so hosts that drop ICMP still answer. website_status gives a one-shot verdict for a website. Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
hoststringyesDomain name or host
portinteger–Port, default 443
NameTypeReqDescription
attempts–––
avgMsnumber|null––
hoststring|null––
ipstring|null––
lossPctnumber|null––
maxMsnumber|null––
minMsnumber|null––
okboolean|null––
portnumber|null––
receivednumber|null––
sentnumber|null––

No examples provided.

port_check ~146

Opens TCP connections to one port or a list of up to 10 ports on a host and reports each as open, closed or filtered, with the time taken. partial=true means the time budget ran out, and `portsNotChecked` lists the ports that were never probed; filtered means no answer arrived, not that the port is certainly closed. TCP only, no UDP. Anonymous, rate-limited per IP; hosts resolving to private or reserved addresses are refused.

NameTypeReqDescription
hoststringyesDomain name or host
port–yesTCP port, or a list of up to 10 ports, e.g. 443 or [80, 443, 25]
NameTypeReqDescription
hoststring|null––
ipstring|null––
okboolean|null––
partialboolean|null––
portnumber|null––
portsNotChecked–––
portsRequestednumber|null––
results–––
statestring|null––
timeMsnumber|null––

No examples provided.

redirect_check ~105

Follows a URL's redirect chain hop by hop and returns each step's status, source and target, the final URL and status, the hop count, and warnings for loops, HTTPS-to-HTTP downgrades and overly long chains. Body and headers of the destination are not returned (http_headers covers headers). Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
urlstringyesFull URL, e.g. https://deinkunde.com
NameTypeReqDescription
finalStatusnumber|null––
finalStatusTextstring|null––
finalUrlstring|null––
hops–––
okboolean|null––
startstring|null––
totalHopsnumber|null––
warnings–––

No examples provided.

response_time ~113

Measures how fast a URL answers over several samples, returning each sample plus min, average and max milliseconds, the HTTP status and an `up` flag. partial=true means fewer samples returned than requested. Measures the HTTP response only: no browser runs, so JavaScript, assets and Core Web Vitals are not reflected. A snapshot, not a trend. Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
urlstringyesFull URL, e.g. https://deinkunde.com
NameTypeReqDescription
avgnumber|null––
maxnumber|null––
minnumber|null––
okboolean|null––
partialboolean|null––
samples–––
samplesRequestednumber|null––
statusnumber|null––
upboolean|null––
urlstring|null––

No examples provided.

reverse_dns ~106

Resolves a public IP address to the PTR hostnames published for it, or returns the resolver's error where there is none. A PTR is set by whoever controls the address block, so it names the host rather than necessarily the site; a missing PTR is common and not a fault. Forward and reverse records need not agree, and this call does not check that they do. Anonymous, rate-limited per IP.

NameTypeReqDescription
ipstringyesPublic IPv4 or IPv6 address
NameTypeReqDescription
errorstring|null––
hostnames–––
ipstring|null––
okboolean|null––

No examples provided.

spf_check ~107

Fetches a domain's SPF record and evaluates it: raw record, parsed terms with qualifiers, DNS lookups counted against the RFC 7208 limit of ten, the final `all` qualifier, and warnings for common silent failures. A domain without a record returns found=false. Alignment and reporting belong to dmarc_check, signing keys to dkim_check. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
allstring|null––
domainstring|null––
errorstring|null––
foundboolean|null––
lookupsnumber|null––
okboolean|null––
recordstring|null––
terms–––
warnings–––

No examples provided.

website_status ~104

Checks whether a website is up right now: up/down verdict, HTTP status and text, response time, server header and number of redirects followed. The usual first call for any is-the-site-down question. A single sample from one location, not uptime; response_time, http_headers and redirect_check go deeper. Anonymous, rate-limited per IP; private and reserved addresses are refused.

NameTypeReqDescription
urlstringyesFull URL, e.g. https://deinkunde.com
NameTypeReqDescription
okboolean|null––
redirectsnumber|null––
responseTimeMsnumber|null––
serverstring|null––
statusnumber|null––
statusTextstring|null––
upboolean|null––
urlstring|null––

No examples provided.

whois ~113

Retrieves WHOIS registration data for a domain: registrar, creation, update and expiry dates, EPP status codes, nameservers and the contact roles the registry still publishes (personal data is usually redacted). tldSupported=false means the TLD has no queryable WHOIS server, which differs from an unregistered domain (found=false). domain_expiry returns the expiry with the remaining days computed. Anonymous, rate-limited per IP.

NameTypeReqDescription
domainstringyesDomain name, e.g. deinkunde.com
NameTypeReqDescription
contacts–––
createdAtstring|null––
domainstring|null––
errorstring|null––
expiresAtstring|null––
foundboolean|null––
nameservers–––
okboolean|null––
registrarstring|null––
statuses–––
tldstring|null––
tldSupportedboolean|null––
updatedAtstring|null––

No examples provided.

Install

How do I install the Uptimeify MCP server?

Uptimeify is a hosted endpoint at https://uptimeify.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 · uptimeify.io

# add to Claude Code
claude mcp add --transport http io-uptimeify-mcp-server 'https://uptimeify.io/mcp'
Common questions

What is the Uptimeify MCP server?

Uptimeify is an MCP server listed in the public MCP registry as io.uptimeify/mcp-server. Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access. This page covers its hosted endpoint (https://uptimeify.io/mcp).

Is the Uptimeify MCP server safe to use?

Uptimeify scores 89 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 Uptimeify MCP server expose?

Uptimeify exposes 20 tools: check_ssl, check_dns, dns_propagation, mx_lookup, spf_check, and 15 more. Their descriptions and schemas cost roughly 2,255 tokens of context every time the server is loaded.

Does the Uptimeify MCP server require authentication?

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

Is the Uptimeify MCP server still maintained?

Uptimeify 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 Uptimeify MCP server?

VerifyMCP ran 13 checks on Uptimeify, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.