dev.workers.mmelnyk2000.well-004-html-to-markdown/html-to-markdown
well-004-html-to-markdown
Is the well-004-html-to-markdown MCP server down? Yes. It has given no valid answer since 2026-10-23: no DNS.
HTML string or https URL to markdown. x402 $0.005 USDC, Base. As is, no warranty.
no DNS down since 2026-10-23 · probed 2026-11-15 · unchanged since 2026-10-26
fetch failed | getaddrinfo ENOTFOUND well-004-html-to-markdown.mmelnyk2000.workers.dev | ENOTFOUND
- Endpoint
- https://well-004-html-to-markdown.mmelnyk2000.workers.dev/mcp (streamable-http)
- Host
- well-004-html-to-markdown.mmelnyk2000.workers.dev
- Website
- https://well-004-html-to-markdown.mmelnyk2000.workers.dev/openapi.json
- Registry
- active, updated 2026-10-16 · registry entry
- Changes
- 3 recorded, reachable in 1 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention markdown.
- ai.artidrop/artidrop · alive
- Web Content & URL Tools ai.avaloncompany/web-content-url-tools · needs auth
- AutEng Docs — Agent Document Workspace & Publishing ai.auteng/docs · alive
- AutEng MCP - Markdown Publishing & Document Share Links ai.auteng/mcp · alive
- file2markdown ai.file2markdown/file2markdown · alive
- Ishan Goyal public context ai.igoyal/public-context · alive
- Keenable Web Search ai.keenable/web-search · alive
- RoboWrite ai.robowrite/mcp · not found
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-23 09:46 | no DNS | ||||
| 2026-10-17 08:02 | alive | 322 ms | 1 | 331 | 196 |
| 2026-10-16 08:50 | server error |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-23, in every probe since then.
- The host name does not resolve. The domain has lapsed or the DNS record is gone.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.