Twenty read-only check tools that run real network probes on demand, with no account and no token: TLS certificate inspection, DNS resolution and propagation, MX lookups, SPF, DKIM and DMARC validation, DNSBL blacklist status, WHOIS and domain expiry, HTTP headers, HSTS, redirect chains, TCP port checks, ping, website status, response time, IP geolocation, ASN lookup and reverse DNS. Point your client at https://uptimeify.io/mcp and start calling. Streamable HTTP, stateless, nothing to configure. Add an Uptimeify API token and five more tools open up, reading your own monitoring data: list_monitors, monitor_status, list_incidents, check_history and uptime_summary. All of them read-only. A customer-scoped token sees a single customer, an organization token sees every customer in the account. OAuth 2.1 with PKCE and Dynamic Client Registration works on the same endpoint, so clients that support it can connect without a token at all. Every probe runs from European infrastructure. Uptimeify is a white-label monitoring platform for agencies and MSPs, built and hosted in Frankfurt, Germany, without US sub-processors. Rate limits: 120 requests per minute per IP across the endpoint, 15 to 30 per minute for each anonymous tool depending on how expensive the probe is, and 60 per minute for each authenticated tool. Limits are enforced per IP, not per token. Exceeding one returns HTTP 429 with a retryAfter value in seconds.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (4647 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 14.5/15 | 29/30 probes succeeded over 30 days (97%). |
| Tool declaration | 10/10 | Lists 20 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 87% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 6% of peers
- This listing 1,092 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/uptimeify/ggez/mcpcurl -X POST https://server.smithery.ai/uptimeify/ggez/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'