io.github.james116blue/journald-mcp-server
Journald MCP Server
Is the Journald MCP server down? Yes. It has given no valid answer since 2026-10-19: install failed.
Incident forensic with log files analyzing
install failed down since 2026-10-19 · probed 2026-11-15 · unchanged since 2026-10-26
hint: `systemd-python` (v235) was included because `journald-mcp-server` (v0.1.0) depends on `systemd-python>=235` hint: Build failures usually indicate a prob
- Run it
- uvx journald-mcp-server@0.1.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/james116blue/journald-mcp-server.git
- Registry
- active, updated 2025-12-19 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.jaimenbell/rag-mcp · alive
- io.github.jaimenbell/rails-mcp · alive
- io.github.jaimenbell/vllm-ops-mcp · alive
- dbprint io.github.jakubro/dbprint · needs args
- Monarch MCP Server io.github.jamiew/monarch-mcp · needs env
- Spotify io.github.jamiew/spotify-mcp · alive
- Unofficial Apple Music for macOS io.github.jaminben/secure-applemusic-mcp-for-osx · install failed
- io.github.janF19/rejstrik-mcp · crashed on start
Servers that mention journald or analyzing or forensic.
- journald cursor shape, value discarded io.github.sadri-dridi/journal-ok · alive
- ai.smithery/plainyogurt21-clintrials-mcp · needs auth
- A.U.G.U.R Synapse · Pump & LP art.maddegen.agent/synapse-pump · alive
- com.dbtrail/dbtrail · no DNS
- Lumethic Photo Verification com.lumethic/verify · needs auth
- com.thetempleofdoom.lynx/lynx · no DNS
- SweetAI — On-chain AI Agent Intelligence com.tiamatcrypto.sweetai/agent-intel · alive
- Freysa Security dev.freysa.economic-agent-369/freysa-intelligence · no DNS
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-19, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.