Uptimeify MCP Server

by uptimeify Your server? Claim it

answering

Uptimeify is answering right now. Last checked 6 min ago. It exposes 20 tools.

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

Uptime history 49 days of history · worst day 99%

49 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

143 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 56

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 12 August 2026. No other catalogue keeps this.

11 Sep 20 tool descriptions were rewritten asn_lookup, check_dns, check_ssl and 17 more

11 Sep a tool changed version

3 Sep 13 tools disappeared alert_history, billing_summary, check_history and 10 more

3 Sep 8 tools appeared alert_history, billing_summary, get_organization and 5 more

3 Sep a tool changed version2 times that day

2 Sep 4 tool descriptions were rewritten check_history, list_monitors, monitor_status and 1 more

2 Sep 3 tools changed the parameters they ask for check_history, list_monitors, monitor_status

2 Sep a tool changed version

12 Aug 3 tool descriptions were rewritten dnsbl_check, port_check, website_status

12 Aug a tool changed the parameters it asks for port_check

and 1 more, back to 12 August 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://uptimeify.io/mcp"
    }
  }
}

~/.codex/config.toml

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

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://uptimeify.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://uptimeify.io/mcp"
    }
  }
}

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dns

check_dns

Resolve a domain's DNS records in one call (A, AAAA, CNAME, MX, TXT, NS, SOA and more), returning each record type with its values and a per-type error where a lookup failed. Answers come from the resolver Uptimeify uses, so this is one vantage point: to see whether the answer is already the same everywhere, use dns_propagation. It reads records only and never connects to the host. Anonymous and rate-limited per IP.

dns_propagation

Query the same domain against several public resolvers and compare the answers, so a recent record change can be told apart from a stale cache. Returns each resolver with the values it gave, plus a consistent flag that stays false while the answers still differ. Use it after changing DNS; for a single reading of all record types, check_dns is the cheaper call. Anonymous and rate-limited per IP.

asn

asn_lookup

Resolve a public IP address, or a domain, to the autonomous system that announces it: AS number and name, the announced prefix, country code, registry and allocation date. Answers who operates the network an address sits on, which tells a hosting provider from a CDN from a corporate network. It does not identify the site owner, and private or reserved addresses have no announcing AS. ip_geolocation returns the same AS data plus country and PTR. Anonymous and rate-limited per IP.

dkim

dkim_check

Fetch and validate the DKIM public key published at a given selector (<selector>._domainkey.<domain>) and report the parsed tags, key type, key size in bits, and warnings such as a revoked or malformed key. The selector is required and cannot be derived from the domain: read it from a message's DKIM-Signature header, or try the provider's usual value (google, selector1, default, k1). An unused selector returns found=false rather than an error. Anonymous and rate-limited per IP.

dmarc

dmarc_check

Fetch a domain's DMARC record from _dmarc.<domain> and evaluate it: the raw record, every parsed tag, the policy and subdomain policy, the percentage the policy applies to, and warnings for records that parse but do not protect (p=none, missing rua, syntax receivers ignore). Reports the published policy, not whether real mail passes it. Pair it with spf_check and dkim_check, the mechanisms DMARC aligns against. Anonymous and rate-limited per IP.

dnsbl

dnsbl_check

Query a public IP address against common DNS blacklists and return, per list, whether it is listed, the reason code the list gave and its delisting URL, plus totals and a clean flag. Takes an IP address, not a domain: resolve the sending host first with mx_lookup or check_dns. Slow blocklists are dropped instead of waited for, so partial=true means zonesQueried is below total and a clean verdict is provisional for the lists that never answered. A listing usually appears between checks, so one call proves only this moment. Anonymous and rate-limited per IP, and this is the strictest limit of the anonymous tools.

domain

domain_expiry

Report a domain's registration expiry from WHOIS together with daysUntilExpiry, plus registrar, creation and update dates and the EPP status codes that reveal a domain already in redemption or pending delete. This is the registration, not the certificate: an expiring TLS certificate is check_ssl. tldSupported=false means the TLD has no WHOIS server Uptimeify can query, which is not the same as an unregistered domain. Anonymous and rate-limited per IP.

geolocation

ip_geolocation

Locate a public IP address, or a domain resolved to one, at network level: country code, allocating registry, announced prefix, PTR hostname and the autonomous systems the address belongs to. It is registry-based, so it names the network operator's country, which for hosted or CDN-fronted addresses is not where the visitor or the business sits -- never read it as a street address. Private and reserved addresses have no answer. For the AS and its owner alone use asn_lookup, for the PTR alone reverse_dns. Anonymous and rate-limited per IP.

hsts

hsts_check

Check a domain's HTTP Strict Transport Security configuration: whether the header is present, its raw value, max-age in seconds, the includeSubDomains and preload flags, whether plain HTTP redirects to HTTPS, whether the configuration would qualify for the browser preload list, and warnings for values that make the header ineffective. Reports the policy the site advertises, not the certificate behind it (check_ssl) and not the full redirect chain (redirect_check). Anonymous and rate-limited per IP; private and reserved address space is refused.

http

http_headers

Fetch a URL and return its HTTP response headers verbatim as a name/value map, with the status line and every redirect hop taken to get there. Use it to inspect caching, security and server headers as they are actually sent; the response body is never returned, so this says nothing about page content. For a plain up/down verdict use website_status, for the redirect chain alone redirect_check. Anonymous and rate-limited per IP; hosts resolving to private or reserved address space are refused.

lookup

mx_lookup

Look up a domain's MX records and resolve each mail exchanger to its IPv4 and IPv6 addresses, ordered by priority and flagged when a host resolves into private address space. Tells you where mail for the domain is delivered; it does not connect to those servers, does not test SMTP, and says nothing about whether the domain is authorised to send (spf_check, dkim_check, dmarc_check). Anonymous and rate-limited per IP.

ping

ping_test

Measure reachability and round-trip time by opening repeated TCP connections to a host, reporting every attempt plus the count sent and received, packet loss percentage and min/avg/max milliseconds. This is a TCP handshake against a port (default 443), not an ICMP echo: a host that drops ICMP still answers here, and a host that answers ICMP with the port closed does not. For a one-shot verdict on a website rather than a latency series, use website_status. Anonymous and rate-limited per IP; private and reserved address space is refused.

port

port_check

Open a TCP connection to one or more ports on a host and report each as open, closed or filtered with the time the attempt took. Pass a single port or a list of up to 10; a single-port call also gets its answer flat, exactly as before the list form existed. partial=true means not every requested port was answered inside the time budget. TCP only -- there is no UDP check -- and filtered means no answer arrived, not that the port is certainly closed. Anonymous and rate-limited per IP; the host is resolved first and private or reserved addresses are refused, including a host whose DNS answer points into them.

redirect

redirect_check

Follow a URL's HTTP redirect chain hop by hop and return every step with its status code, source and target, the final URL and status, the hop count, and warnings for chains that loop, drop from HTTPS to HTTP, or run longer than they should. Answers where a URL ends up and how many round trips that costs; it returns neither the body nor the headers of the destination (http_headers). Anonymous and rate-limited per IP; private and reserved address space is refused.

response

response_time

Measure how fast a URL answers by taking several samples and returning each one plus min, average and max milliseconds, the HTTP status and an up flag. partial=true means fewer samples came back than were requested, so the average rests on a smaller base. This measures the response, not the rendered page: no browser runs, so nothing here reflects JavaScript, assets or Core Web Vitals. One call is a snapshot, not a trend. Anonymous and rate-limited per IP; private and reserved address space is refused.

reverse

reverse_dns

Resolve a public IP address to the PTR hostnames published for it, returning every name the pointer record carries, or 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 running on it, and a missing PTR is common and not a fault. It is not the inverse of check_dns: a forward record and a PTR need not agree, and this call does not verify that they do. Anonymous and rate-limited per IP.

spf

spf_check

Fetch a domain's SPF record and evaluate the policy: the raw record, every parsed term with its qualifier, the number of DNS lookups it costs against the RFC 7208 limit of ten, the final all qualifier, and warnings for the failure modes that silently break sending. Covers the sending policy only -- alignment and reporting are DMARC (dmarc_check), the signing key is DKIM (dkim_check). A domain without a record returns found=false, which is an answer, not an error. Anonymous and rate-limited per IP.

ssl

check_ssl

Fetch and evaluate a host's TLS/SSL certificate over a live handshake: subject and 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, plus an optional port (default 443). This is a single sample taken now: it does not watch the certificate over time, says nothing about the HTTP response behind it (website_status) and nothing about the transport policy the site advertises (hsts_check). Anonymous and rate-limited per IP; hosts that resolve to private or reserved address space are refused.

website

website_status

Is a website up right now? Start here for any is-the-site-down question: up/down verdict, HTTP status and status text, response time in milliseconds, the server header and the number of redirects followed, in one call. This is a single sample from one location taken now -- it is not uptime, and a site that fails here may be reachable from elsewhere. For the timing breakdown use response_time, for the headers themselves http_headers, for the redirect chain redirect_check. Anonymous and rate-limited per IP; private and reserved address space is refused.

whois

whois

Retrieve WHOIS registration data for a domain: registrar, creation, update and expiry dates, EPP status codes, nameservers and the contact roles the registry still publishes. Registries redact personal data since GDPR, so contacts are usually roles without names. Not every TLD has a WHOIS server Uptimeify can query -- tldSupported=false means it could not ask, which is different from a domain that is not registered (found=false). For the expiry date alone, domain_expiry returns it with the remaining days already computed. Anonymous and rate-limited per IP.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

alert_history

removed 3 Sep 2026

billing_summary

removed 3 Sep 2026

check_history

removed 3 Sep 2026

get_organization

removed 3 Sep 2026

list_alert_channels

removed 3 Sep 2026

list_customers

removed 3 Sep 2026

list_incidents

removed 3 Sep 2026

list_maintenance_windows

removed 3 Sep 2026

list_monitors

removed 3 Sep 2026

list_status_pages

removed 3 Sep 2026

list_users

removed 3 Sep 2026

monitor_status

removed 3 Sep 2026

uptime_summary

removed 3 Sep 2026

Endpoints

URL	Transport	State	Latency	Checked
https://uptimeify.io/mcp	streamable-http	answering	143 ms	6 min ago

Alternatives to Uptimeify

same job, measured the same way

Agent Health

by autonet

Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.

21 tools answering

Orbilo

by orbilo

Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.

5 tools answering

Wachete

by wachete

Create, read and monitor Wachete website-change wachets for a signed-in user.

answering

HostTracker

by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering

YoPingMe uptime monitoring

by yoping

Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks

answering

Watchpup

by workers-watchpup-watchpup

Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.

12 tools answering

Lumin

by getlumin

Read-only access to a Lumin project's logs, metrics, uptime checks, alerts and infrastructure.

answering

Uptimepage

by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

31 tools answering

Uptimeify — questions

Answers built from our own checks of this server.

What can Uptimeify do?

It exposes 20 tools, read directly from the server on our last check. Among them: asn_lookup, check_dns, check_ssl, dkim_check, dmarc_check, dnsbl_check and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Uptimeify working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 143 ms. The bar chart above shows every period we have measured.

Did Uptimeify ever remove tools?

Yes. alert_history, billing_summary, check_history, get_organization and 9 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect Uptimeify?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Uptimeify need an API key?

No. Uptimeify completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Uptimeify?

It answers our handshake in 143 ms on average, which is faster than 79% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.