io.github.Herzog-GmbH/blp-mcp
ACTIWARE BLP (ELO Sidebar)
Is the ACTIWARE BLP (ELO Sidebar) MCP server down? It gave no valid answer in the probe of 2026-11-12: not found. One failed probe is not an outage.
ACTIWARE BLP: read and change ELO sidebar processes, objects, tabs and tiles, with preview
not found no valid answer since 2026-11-12 · probed 2026-11-15 · unchanged since 2026-11-12
command not found: pwsh.exe
- Bundle
- https://github.com/Herzog-GmbH/blp-mcp/releases/download/v0.9.0/blp-mcp-0.9.0.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/Herzog-GmbH/blp-mcp
- Website
- https://github.com/Herzog-GmbH/blp-mcp
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- io.github.Hafeok/product-cli · install failed
- Notes by Halo io.github.Halo-Software/notes-by-halo-mcp · needs env
- Hawkeye AI Bridge io.github.Hawkeye-Zaragsoft/hawkeye-aibridge · error
- ACMP MCP Server io.github.Herzog-GmbH/acmp-mcp · not found
- ELO ECM io.github.Herzog-GmbH/elo-mcp · not found
- Archytan Lite MCP gate io.github.High-ArchyTech-Solutions/archytan-mcp-gate · needs env
- KatanA Markdown Linter io.github.HiroyukiFuruno/kml · crashed on start
- Horosa Skill io.github.Horace-Maxwell/horosa-skill · crashed on start
Servers that mention actiware or sidebar.
- io.github.mmedum/google-chat-mcp · alive
- Covate io.github.SunflowersLwtech/covate · alive
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
- The package did not start as an MCP server at its probe on 2026-11-12. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- 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.