io.github.jarmstrong158/Conductor
io.github.jarmstrong158/Conductor
Is the io.github.jarmstrong158/Conductor MCP server down? No. It is up and needs network, probed 2026-10-31.
Local task scheduler and worker manager with MCP integration for Claude Desktop.
needs network probed 2026-11-15 · unchanged since 2026-10-31
MCP error -32000: Connection closed OSError: [Errno 30] Read-only file system: '/work/uv/conductor-mcpserver/lib/python3.12/site-packages/templates' FileNotFoun
- Run it
- uvx conductor-mcpserver@4.0.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/jarmstrong158/Conductor
- Registry
- active, updated 2026-08-02 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.janF19/rejstrik-mcp · crashed on start
- Tistory MCP (Unofficial) io.github.jangsejong/tistory-mcp · alive
- H-1B Sponsor io.github.janishkumar/h1b-sponsor-mcp · alive
- io.github.janus-ubos-republic/janus-kinematic-drive · alive
- agentsync io.github.jarmstrong158/agentsync · alive
- Cambium io.github.jarmstrong158/cambium · alive
- io.github.jarmstrong158/context-keeper · alive
- io.github.jarmstrong158/skillmatch-mcp · crashed on start
Servers that mention conductor.
- Wafergraph MCP com.wafergraph/wafergraph-mcp · alive
- Silicon Analysts io.github.SiliconAnalysts/silicon-analysts · alive
- Conductor Relay MCP io.github.Zman504/conductor-relay-mcp · alive
- io.github.codebiwan/semi-data · alive
- SEAR io.github.igor-holt/sear · not MCP
- io.tooloracle/conductor · alive
- Silicon Almanac com.siliconalmanac/record · alive
- io.github.base76-research-lab/conductor-graph-mcp · crashed on start
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-31 07:37 | needs network | ||||
| 2026-10-17 06:16 | crashed on start |
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 server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.