io.github.nicksull/mac-organiser-mcp
io.github.nicksull/mac-organiser-mcp
Is the io.github.nicksull/mac-organiser-mcp MCP server down? Yes. It has given no valid answer since 2026-10-31: install failed.
Privacy-focused MCP server for Apple Reminders, Calendar and Notes on macOS.
install failed down since 2026-10-31 · probed 2026-11-15 · unchanged since 2026-11-08
npm error notsup Valid os: darwin npm error notsup Actual os: linux npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-15T08_32_54_
- Run it
- npx -y mac-organiser-mcp@0.2.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/nicksull/mac-organiser-mcp
- Registry
- active, updated 2026-10-30 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.nickjlamb/studydiff · alive
- io.github.nickjlucker/greynoise · alive
- io.github.nicklasmenschel/gerezi-mcp · alive
- io.github.nickoc/bearing-local-business · alive
- io.github.nicktcode/swissgroceries-mcp · alive
- bash-mcp io.github.nickw8/bash-mcp · alive
- io.github.nickymitnick/probo-connect-mcp · alive
- io.github.nickzitzer/servicenow-nodejs · crashed on start
Servers that mention organiser.
- ai.tickettailor/mcp · needs auth
- EventMatey Event Discovery com.eventmatey.mcp/event-discovery · alive
- Events Data io.github.projectworks007/events-data · needs auth
- Open Paddock app.openpaddock/open-paddock · alive
- Dandori life.dandori/dandori · needs auth
- CBO MCP by usefulapi io.usefulapi/cloud-business-organiser · timeout
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-31, 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.