Domain Liveness

Is this business's website still there? Checks apex and www, and DNS separately from HTTP.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~145Tokens (tool definitions)
~480 BTypical response size
Minimal attention impact (0.11% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "domain-liveness": {
      "url": "https://domain-liveness-mcp.ottobot2025.workers.dev/mcp"
    }
  }
}

Remote endpoints

https://domain-liveness-mcp.ottobot2025.workers.dev/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_domain_live(domain)

Is this business's website still there? Checks the apex AND www, resolves DNS over HTTPS independently of web requests, falls back to plain HTTP, and separates four things a status code conflates: the name does not resolve, the check itself failed, a recognized parked/suspended/for-sale page answers, and the site refuses bots. Read-only. Will not claim a live page belongs to a different business than the one you asked about.

Input Schema

{
  "type": "object",
  "properties": {
    "domain": {
      "type": "string",
      "description": "A hostname or URL, e.g. example.com or https://www.example.com"
    }
  },
  "required": [
    "domain"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools
verifiedversion not recorded1 tools