io.github.n24q02m/workspace
io.github.n24q02m/workspace
Is the io.github.n24q02m/workspace MCP server down? It gave no valid answer in the probe of 2026-11-13: timeout. One failed probe is not an outage.
Google Workspace MCP — Docs, Drive, Calendar, Gmail, Sheets, Slides, Tasks, Chat, People, Forms
timeout no valid answer since 2026-11-13 · probed 2026-11-14 · unchanged since 2026-11-13
probe timed out after 45000 ms [workspace] Google authorization required. Open http://127.0.0.1:34117/ in a browser to continue.
- Run it
- npx -y @n24q02m/workspace@0.7.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/n24q02m/workspace
- Registry
- active, updated 2026-11-12 · 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.n24q02m/better-notion-mcp · crashed on start
- io.github.n24q02m/better-workspace-mcp · timeout
- io.github.n24q02m/email · alive
- io.github.n24q02m/notion · crashed on start
- r3 io.github.n3wth/r3 · alive
- io.github.nailuoGG/anki-mcp-server · crashed on start
- io.github.nakishiyaman/dig · alive
- io.github.namtran/diskcleankit-mcp · alive
Servers that mention workspace.
- AutEng Docs — Agent Document Workspace & Publishing ai.auteng/docs · alive
- Bindry ai.bindry/bindry · needs auth
- ai.bridgeapp/bridgeapp · needs auth
- Calaf Seed Tools ai.calaf/seeds · alive
- Dryos Workspace ai.dryos/dryos-workspace · needs auth
- ai.enginy/mcp · needs auth
- Filepad ai.filepad/filepad · server error
- Kive ai.kive/mcp · 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
- The package did not start as an MCP server at its probe on 2026-11-13. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- No answer within 15 seconds. The server is up but slow, or the request hangs. Some servers stall tools/list while a GET stream is open; the probe opens none.