org.ottobotPublished by ottobot.orgv0.1.0Updated Oct 27, 2026
Is this business's website still there? Checks apex and www, and DNS separately from HTTP.
The publisher's own server: QR Rápido
Remote MCP server that checks whether a business's website is still live, testing apex and www domains with separate DNS and HTTP lookups.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/org.ottobot%2Fdomain-liveness/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"domain-liveness": {
"type": "http",
"url": "https://domain-liveness-mcp.ottobot2025.workers.dev/mcp"
}
}
}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
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:
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
go directive in go.mod; the Go toolchain fetches it for yougolangci-lint-action pin in ci.yml, so local lint matches CIThis 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 MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via MCP_REGISTRY_DATABASE_URL (see docker-compose.yml for a working example):
Available tags:
latest, v1.0.0, v1.1.0, etc.main (latest main branch build)main-<date>-<sha> (specific commit builds)Publishing an MCP server does not happen through a pull request to this repository. Adding a server.json, a server directory, or an entry in data/seed.json will not publish or list your server, even if the PR is merged. Use the mcp-publisher CLI from your server's own project instead.
To publish a server, we've built a simple CLI. You can use it with:
See the publisher guide for more details.
There are also a few more helpful commands for development. Run make help to learn more, or look in Makefile.
Publishing supports multiple authentication methods:
The registry validates namespace ownership when publishing. E.g. to publish...:
io.github.domdomegg/my-cool-mcp you must login to GitHub as domdomegg, or be in a GitHub Action on domdomegg's reposme.adamjones/my-cool-mcp you must prove ownership of adamjones.me via DNS or HTTP challengeCheck out community projects to explore notable registry-related work created by the community.
See the documentation for more details if your question has not been answered here!
Source: README.md at commit 11b7b0e
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.
domainrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
site.qrrapidoOfficial publisher
A remote MCP server that lets an assistant generate QR codes for URLs, PIX payments, Wi-Fi, vCards, WhatsApp and similar targets.
ai.com.mcpOfficial publisher
A remote MCP registry server that lets an assistant browse registered MCP servers, their versions, and version details.
org.ottobot
A remote MCP server that checks a business website's contact path and reports whether a human can actually reach it.
# Start full development environmentmake dev-compose# Run latest stable releasedocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
# Run latest from main branch (continuous deployment)docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
# Run specific release versiondocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
# Run development build from main branchdocker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d# Build the latest CLImake publisher
# Use it!./bin/mcp-publisher --help# Run lint, schema validation, and all tests# Note: this also runs `make dev-down`, stopping any running dev-compose environmentmake check├── cmd/ # Application entry points│ ├── publisher/ # Server publishing tool│ └── registry/ # Registry API server├── data/ # Seed data├── deploy/ # Deployment configuration (Pulumi)├── docs/ # Documentation├── internal/ # Private application code│ ├── api/ # HTTP handlers and routing│ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)│ ├── config/ # Configuration management│ ├── database/ # Data persistence (PostgreSQL)│ ├── importer/ # Seed data import│ ├── service/ # Business logic│ ├── telemetry/ # Metrics and monitoring│ └── validators/ # Input validation├── pkg/ # Public packages│ ├── api/ # API types and structures│ │ └── v0/ # Version 0 API types│ └── model/ # Data models for server.json├── scripts/ # Development and testing scripts├── tests/ # Integration tests└── tools/ # CLI tools and utilities └── validate-*.sh # Schema validation tools