Uptimeify
REMOTE · UPTIMEIFY.IO · SCANNED SEP 24
Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 20 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2702 tokens (~135/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 Management80
- Stability check failed: schema churn in the 30 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
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
claude mcp add --transport http io-uptimeify-mcp-server 'https://uptimeify.io/mcp'
{
"mcpServers": {
"io-uptimeify-mcp-server": {
"url": "https://uptimeify.io/mcp"
}
}
} {
"servers": {
"io-uptimeify-mcp-server": {
"type": "http",
"url": "https://uptimeify.io/mcp"
}
}
} [mcp_servers.io-uptimeify-mcp-server] url = "https://uptimeify.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-uptimeify-mcp-server": {
"type": "remote",
"url": "https://uptimeify.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-uptimeify-mcp-server --url 'https://uptimeify.io/mcp' --transport streamable-http
mcp_servers:
io-uptimeify-mcp-server:
url: "https://uptimeify.io/mcp" {
"McpServers": {
"io-uptimeify-mcp-server": {
"Transport": "http",
"Url": "https://uptimeify.io/mcp"
}
}
} assistant mcp add io-uptimeify-mcp-server -t streamable-http -u 'https://uptimeify.io/mcp'
{
"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.
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.
- 11 Sept 26 −1
- Tool “asn_lookup” rewrote its description, which is the text the model reads security
- Tool “check_dns” rewrote its description, which is the text the model reads security
- Tool “check_ssl” rewrote its description, which is the text the model reads security
- Tool “dkim_check” rewrote its description, which is the text the model reads security
- Tool “dmarc_check” rewrote its description, which is the text the model reads security
- Tool “dns_propagation” rewrote its description, which is the text the model reads security
- Tool “dnsbl_check” rewrote its description, which is the text the model reads security
- Tool “domain_expiry” rewrote its description, which is the text the model reads security
- Tool “hsts_check” rewrote its description, which is the text the model reads security
- Tool “http_headers” rewrote its description, which is the text the model reads security
- Tool “ip_geolocation” rewrote its description, which is the text the model reads security
- Tool “mx_lookup” rewrote its description, which is the text the model reads security
- Tool “ping_test” 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
- Tool “redirect_check” rewrote its description, which is the text the model reads security
- Tool “response_time” rewrote its description, which is the text the model reads security
- Tool “reverse_dns” rewrote its description, which is the text the model reads security
- Tool “spf_check” rewrote its description, which is the text the model reads security
- Tool “website_status” rewrote its description, which is the text the model reads security
- Tool “whois” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 1.4.1 → 1.6.0 functional
- 3 Sept 26 −2
- Stability: 0.97 → fail ▼ security
- Tool “alert_history” was removed ▼ security
- Tool “billing_summary” was removed ▼ security
- Tool “check_history” was removed ▼ security
- Tool “get_organization” was removed ▼ security
- Tool “list_alert_channels” was removed ▼ security
- Tool “list_customers” was removed ▼ security
- Tool “list_incidents” was removed ▼ security
- Tool “list_maintenance_windows” was removed ▼ security
- Tool “list_monitors” was removed ▼ security
- Tool “list_status_pages” was removed ▼ security
- Tool “list_users” was removed ▼ security
- Tool “monitor_status” was removed ▼ security
- Tool “uptime_summary” was removed ▼ security
- Stability: 0.97 → pass security
- Tool “check_history” rewrote its description, which is the text the model reads security
- Tool “list_monitors” rewrote its description, which is the text the model reads security
- Tool “monitor_status” rewrote its description, which is the text the model reads security
- Tool “uptime_summary” rewrote its description, which is the text the model reads security
- Schema quality: 47 → 80 ▼ functional
- Schema quality: 47 → 56 ▼ functional
- Schema quality: 1179 → 918 ▲ functional
- Server version: 1.4.0 → 1.4.1 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “alert_history” functional
- New tool “billing_summary” functional
- New tool “get_organization” functional
- New tool “list_alert_channels” functional
- New tool “list_customers” functional
- New tool “list_maintenance_windows” functional
- New tool “list_status_pages” functional
- New tool “list_users” functional
- “check_history” added an optional parameter “kind” cosmetic
- “list_monitors” added an optional parameter “kind” cosmetic
- “monitor_status” added an optional parameter “kind” cosmetic
- “check_history” reworded the description of “monitor_id” cosmetic
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Aug 26 0
- 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
- Tool “website_status” rewrote its description, which is the text the model reads security
- “port_check” reworded the description of “port” cosmetic
- 11 Aug 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
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 24 Sept 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 | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 67dca7e974b96a1e7f8119b598831052245 |
| 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. | present | 57355 | 8 | Verified |
| uptimeify.io. | present | 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 | base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; 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 |
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 →
asn_lookup ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Public IP address or domain name |
| Name | Type | Req | Description |
|---|---|---|---|
| asns | – | – | – |
| cc | string|null | – | – |
| found | boolean|null | – | – |
| ip | string|null | – | – |
| ok | boolean|null | – | – |
| prefix | string|null | – | – |
| query | string|null | – | – |
| registry | string|null | – | – |
No examples provided.
check_dns ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | – | – |
| found | boolean|null | – | – |
| ok | boolean|null | – | – |
| records | – | – | – |
| warnings | – | – | – |
No examples provided.
check_ssl ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Domain name (not an IP), e.g. deinkunde.com |
| port | integer | – | TLS port, default 443 |
| Name | Type | Req | Description |
|---|---|---|---|
| authorizationError | string|null | – | – |
| daysUntilExpiry | number|null | – | – |
| expired | boolean|null | – | – |
| fingerprint256 | string|null | – | – |
| found | boolean|null | – | – |
| host | string|null | – | – |
| hostnameMatch | boolean|null | – | – |
| ip | string|null | – | – |
| issuerCN | string|null | – | – |
| issuerO | string|null | – | – |
| notYetValid | boolean|null | – | – |
| ok | boolean|null | – | – |
| port | number|null | – | – |
| san | – | – | – |
| selfSigned | boolean|null | – | – |
| serialNumber | string|null | – | – |
| subjectCN | string|null | – | – |
| trusted | boolean|null | – | – |
| validFrom | string|null | – | – |
| validTo | string|null | – | – |
No examples provided.
dkim_check ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| selector | string | yes | DKIM selector, e.g. google or default |
| Name | Type | Req | Description |
|---|---|---|---|
| bits | number|null | – | – |
| domain | string|null | – | – |
| error | string|null | – | – |
| found | boolean|null | – | – |
| hasKey | boolean|null | – | – |
| keyType | string|null | – | – |
| ok | boolean|null | – | – |
| record | string|null | – | – |
| selector | string|null | – | – |
| tags | – | – | – |
| warnings | – | – | – |
No examples provided.
dmarc_check ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | – | – |
| error | string|null | – | – |
| found | boolean|null | – | – |
| ok | boolean|null | – | – |
| pct | number|null | – | – |
| policy | string|null | – | – |
| record | string|null | – | – |
| subPolicy | string|null | – | – |
| tags | – | – | – |
| warnings | – | – | – |
No examples provided.
dns_propagation ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| consistent | boolean|null | – | – |
| domain | string|null | – | – |
| ok | boolean|null | – | – |
| results | – | – | – |
| type | string|null | – | – |
No examples provided.
dnsbl_check ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | Public IPv4 or IPv6 address |
| Name | Type | Req | Description |
|---|---|---|---|
| clean | boolean|null | – | – |
| ip | string|null | – | – |
| listedCount | number|null | – | – |
| ok | boolean|null | – | – |
| partial | boolean|null | – | – |
| results | – | – | – |
| total | number|null | – | – |
| zonesQueried | number|null | – | – |
No examples provided.
domain_expiry ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| createdAt | string|null | – | – |
| daysUntilExpiry | number|null | – | – |
| domain | string|null | – | – |
| error | string|null | – | – |
| expiresAt | string|null | – | – |
| found | boolean|null | – | – |
| ok | boolean|null | – | – |
| registrar | string|null | – | – |
| statuses | – | – | – |
| tld | string|null | – | – |
| tldSupported | boolean|null | – | – |
| updatedAt | string|null | – | – |
No examples provided.
hsts_check ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | – | – |
| httpsRedirect | boolean|null | – | – |
| includeSubDomains | boolean|null | – | – |
| maxAge | number|null | – | – |
| ok | boolean|null | – | – |
| preload | boolean|null | – | – |
| preloadReady | boolean|null | – | – |
| present | boolean|null | – | – |
| raw | string|null | – | – |
| warnings | – | – | – |
No examples provided.
http_headers ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL, e.g. https://deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| headers | – | – | – |
| ok | boolean|null | – | – |
| redirects | – | – | – |
| status | number|null | – | – |
| statusText | string|null | – | – |
| url | string|null | – | – |
No examples provided.
ip_geolocation ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Public IP address or domain name |
| Name | Type | Req | Description |
|---|---|---|---|
| asns | – | – | – |
| cc | string|null | – | – |
| found | boolean|null | – | – |
| ip | string|null | – | – |
| ok | boolean|null | – | – |
| prefix | string|null | – | – |
| ptr | string|null | – | – |
| query | string|null | – | – |
| registry | string|null | – | – |
| resolvedFromDomain | boolean|null | – | – |
No examples provided.
mx_lookup ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | – | – |
| found | boolean|null | – | – |
| ok | boolean|null | – | – |
| servers | – | – | – |
No examples provided.
ping_test ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Domain name or host |
| port | integer | – | Port, default 443 |
| Name | Type | Req | Description |
|---|---|---|---|
| attempts | – | – | – |
| avgMs | number|null | – | – |
| host | string|null | – | – |
| ip | string|null | – | – |
| lossPct | number|null | – | – |
| maxMs | number|null | – | – |
| minMs | number|null | – | – |
| ok | boolean|null | – | – |
| port | number|null | – | – |
| received | number|null | – | – |
| sent | number|null | – | – |
No examples provided.
port_check ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Domain name or host |
| port | – | yes | TCP port, or a list of up to 10 ports, e.g. 443 or [80, 443, 25] |
| Name | Type | Req | Description |
|---|---|---|---|
| host | string|null | – | – |
| ip | string|null | – | – |
| ok | boolean|null | – | – |
| partial | boolean|null | – | – |
| port | number|null | – | – |
| portsRequested | number|null | – | – |
| results | – | – | – |
| state | string|null | – | – |
| timeMs | number|null | – | – |
No examples provided.
redirect_check ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL, e.g. https://deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| finalStatus | number|null | – | – |
| finalStatusText | string|null | – | – |
| finalUrl | string|null | – | – |
| hops | – | – | – |
| ok | boolean|null | – | – |
| start | string|null | – | – |
| totalHops | number|null | – | – |
| warnings | – | – | – |
No examples provided.
response_time ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL, e.g. https://deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| avg | number|null | – | – |
| max | number|null | – | – |
| min | number|null | – | – |
| ok | boolean|null | – | – |
| partial | boolean|null | – | – |
| samples | – | – | – |
| samplesRequested | number|null | – | – |
| status | number|null | – | – |
| up | boolean|null | – | – |
| url | string|null | – | – |
No examples provided.
reverse_dns ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | Public IPv4 or IPv6 address |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string|null | – | – |
| hostnames | – | – | – |
| ip | string|null | – | – |
| ok | boolean|null | – | – |
No examples provided.
spf_check ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| all | string|null | – | – |
| domain | string|null | – | – |
| error | string|null | – | – |
| found | boolean|null | – | – |
| lookups | number|null | – | – |
| ok | boolean|null | – | – |
| record | string|null | – | – |
| terms | – | – | – |
| warnings | – | – | – |
No examples provided.
website_status ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL, e.g. https://deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean|null | – | – |
| redirects | number|null | – | – |
| responseTimeMs | number|null | – | – |
| server | string|null | – | – |
| status | number|null | – | – |
| statusText | string|null | – | – |
| up | boolean|null | – | – |
| url | string|null | – | – |
No examples provided.
whois ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name, e.g. deinkunde.com |
| Name | Type | Req | Description |
|---|---|---|---|
| contacts | – | – | – |
| createdAt | string|null | – | – |
| domain | string|null | – | – |
| error | string|null | – | – |
| expiresAt | string|null | – | – |
| found | boolean|null | – | – |
| nameservers | – | – | – |
| ok | boolean|null | – | – |
| registrar | string|null | – | – |
| statuses | – | – | – |
| tld | string|null | – | – |
| tldSupported | boolean|null | – | – |
| updatedAt | string|null | – | – |
No examples provided.
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 79 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,702 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.