Home / MCP registry index / io.uptimeify/mcp-server
Uptimeify
io.uptimeify/mcp-server in the official MCP registry.
Endpoint https://uptimeify.io/mcp.
The registry describes it as: Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
We read its 20 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
check_ssl check_dns dns_propagation mx_lookup spf_check dkim_check dmarc_check dnsbl_check whois domain_expiry http_headers hsts_check redirect_check port_check ping_test website_status response_time ip_geolocation asn_lookup reverse_dns
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-uptimeify-mcp-server)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.