io.github.kreuzberg-dev/kreuzcrawl
Kreuzcrawl
Is the Kreuzcrawl MCP server down? Yes. It has given no valid answer since 2026-11-04: not found.
Scrape, crawl, and map websites to Markdown or JSON via local CLI.
not found down since 2026-11-04 · probed 2026-11-15 · unchanged since 2026-11-11
Error response from daemon: error from registry: denied denied
- Run it
- docker run -i --rm ghcr.io/kreuzberg-dev/kreuzcrawl:0.3.0 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Repository
- https://github.com/kreuzberg-dev/kreuzcrawl
- Website
- https://kreuzberg.dev
- Registry
- active, updated 2026-06-23 · registry entry
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Tiny Go MCP Server io.github.kioie/tiny-go-mcp · alive
- Rogue Binary MCP io.github.kirkderp/rbinmcp · not found
- Scout io.github.klarlabs-studio/scout · alive
- koment io.github.koment-dev/koment · crashed on start
- Mini Data Engine Runtime Copilot io.github.kroq86/mini-data-engine · alive
- Vector DB MCP io.github.kroq86/vector-db-mcp · alive
- BAND io.github.ktgeek/band-mcp-server · alive
- io.github.kubeleash/kubeleash · needs env
Servers that mention markdown or websites.
- 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
- Augenix ai.augenix/build · alive
- AutEng MCP - Markdown Publishing & Document Share Links ai.auteng/mcp · alive
- Cactal ai.cactal/cactal · alive
- file2markdown ai.file2markdown/file2markdown · alive
- HostingFor.AI ai.hostingfor/hosting · needs auth
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-11-04, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.