MCP.Market

Domain Liveness MCP server

online · 100% uptime
by ottobot.org·org.ottobot/domain-liveness·v0.1.0·7.4k stars
No reviews yet

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

A88/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
Established

7.4k stars

Reviews

Write one

Nobody has reviewed Domain Liveness yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Domain Liveness tools (1)

write = sends, deletes, buys or posts
  • check_domain_liveFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-15 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 290ms20/20
  • Tool poisoning1 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Domain Liveness compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
43 ms
faster than 93% of 30,031 servers
GitHub stars
7,365
more than 95% of 28,688 servers

What its tools let an agent do: 1 read

Install Domain Liveness in Claude Code, Cursor or VS Code

claude mcp add --transport http domain-liveness https://domain-liveness-mcp.ottobot2025.workers.dev/mcp
Add to Cursor

What the publisher says

From the Domain Liveness repository's README, as published. We do not edit it. Read it on GitHub

MCP Registry

The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.

📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation

Development Status

2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!

2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).

Registry Working Group:

  • Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov - WG Lead
  • Tadas Antanavicius (PulseMCP) @tadasant
  • Bob Dickinson (TeamSpark) @BobDickinson
  • Preeti (Pree) Dewani (Ravenmail) @pree-dew

Contributing

We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.

Often (but not always) ideas flow through this pipeline:

  • Discord - Real-time community discussions
  • Discussions - Propose and discuss product/technical requirements
  • Issues - Track well-scoped technical work
  • Pull Requests - Contribute work towards issues

Quick start:

Pre-requisites

  • Docker
  • Go - version per the go directive in go.mod; the Go toolchain fetches it for you
  • ko - Container image builder for Go (installation instructions)
  • golangci-lint - version per the golangci-lint-action pin in ci.yml, so local lint matches CI

Running the server

# Start full development environment
make dev-compose

This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.

Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.

By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRY_VALIDATION=false make dev-compose.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Domain Liveness: common questions

Is Domain Liveness MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Domain Liveness safety report
How do I install Domain Liveness?
It runs remotely at domain-liveness-mcp.ottobot2025.workers.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Domain Liveness need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Domain Liveness maintained?
The last commit was 20 days ago (2026-10-14). The latest release is v0.1.0.
Is Domain Liveness up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Domain Liveness?
Servers from other publishers that do the same job: Business Contact Finder MCP server.
How does Domain Liveness compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Domain Liveness

Same job from other publishers: the closest match first, then the best rated.

  • Business Contact Finder
    Check how to contact a business website, and whether that contact path actually works.
    A