com.olane/cosync-local
com.olane/cosync-local
Is the com.olane/cosync-local MCP server down? Yes. It has given no valid answer since 2026-10-20: not found.
Local encryption and project setup plugin for CoSync. Keys never leave your machine.
not found down since 2026-10-20 · probed 2026-11-14 · unchanged since 2026-10-27
error: No solution found when resolving dependencies cause: Because olane-cosync-local was not found in the package registry and you require olane-cosync-loca
- Run it
- uvx olane-cosync-local@0.2.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/olane-labs/cosync-local
- Registry
- active, updated 2026-03-04 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- com.munimind/munimind-mcp · crashed on start
- Holster MCP com.nautaai/holster-mcp · alive
- Less Annoying CRM com.northkeellabs/lacrm-mcp · alive
- com.olane/copass-local · alive
- com.opensolr/opensolr-mcp · alive
- com.opsmill/infrahub-mcp · install failed
- The Korova Milk Bar com.philstuff.korova/mcp · alive
- com.pitbridge/pitbridge · needs mcp<2
Servers that mention cosync or encryption or machine.
- com.olane/cosync-remote · no DNS
- One-Page Readiness Check — 10 Signals, Arabic or English ai.advisorsai/store-readiness · alive
- ConnectMachine ai.connectmachine/connectmachine · needs auth
- JackHamr ai.jackhamr/jackhamr · needs auth
- Machine Relations Index ai.machinerelations/mri · alive
- SentEdge Idea Machine ai.sentedge/idea-machine · alive
- TensorFeed ai.tensorfeed/mcp-server · alive
- Time Machine ai.timeml/time-machine · 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-10-20, 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.