UptimeGuard — Live Website & API Availability, DNS, Headers, TLS & Content-Drift Monitoring

https://server.smithery.ai/tofan96you/uptimeguard-mcp/mcp

● healthy

Live website and API operational health engine for developers, agencies and site owners. Run real HTTP availability checks with status, latency, redirects, content type and response evidence; inspect DNS A, AAAA, MX and NS resolution; audit live security, caching and delivery headers; review HTTPS transport readiness and renewal guidance; compare a live response with an expected content marker to detect unexpected deployment changes; and generate a prioritized PASS, WARNING or DOWN operational report with source timestamps and recommended actions. No API key required. Free tier: 10 requests/day. A live snapshot is not a historical uptime SLA measurement and should be combined with repeated monitoring for availability guarantees.

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2024-11-05

negotiated, not declared

MCP readiness

B · 83/100

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 (4395 ms); slow response -1.
Protocol revision	5/10	Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 7 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.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (4395 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

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 60% of peers; This listing 83 · peer median 81
Latency: Faster than 12% of peers; This listing 821 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Protocol revision −5 — Support the current protocol revision.
Now: Speaks MCP 2024-11-05, 4 revision(s) behind 2026-07-28.
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.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-10-12 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/tofan96you/uptimeguard-mcp/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/tofan96you/uptimeguard-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://uptimeguard73-api.agentweb-hub.workers.dev/

Listed at (smithery)

https://uptimeguard73-api.agentweb-hub.workers.dev/