io.github.AIWerk/mcp-server-cal
io.github.AIWerk/mcp-server-cal
Is the io.github.AIWerk/mcp-server-cal MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Cal.com scheduling MCP server: manage bookings, event types, and availability.
not found down since 2026-10-16 · probed 2026-11-14 · unchanged since 2026-10-30
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @aiwerk/mcp-server-cal@1.0.6 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/AIWerk/mcp-server-cal
- Website
- https://aiwerkmcp.com/servers/cal/
- Registry
- active, updated 2026-06-22 · 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.AINative-Studio/ainative-strapi-mcp-server · alive
- io.github.AINative-Studio/ainative-zerodb-memory-mcp · alive
- AIPost MCP Server io.github.AIPOST-EMAIL/mcp-server · alive
- AIVeed io.github.AIVeed-io/aiveed-mcp · alive
- io.github.AIWerk/mcp-server-clawhub · not found
- io.github.AIWerk/mcp-server-imap · not found
- io.github.AIWerk/mcp-server-shopify · not found
- io.github.AIWerk/mcp-server-vault · not found
Servers that mention aiwerk or availability or scheduling.
- io.github.AIWerk/mcp-server-wheel-size · not found
- io.github.AIWerk/mcp-server-wise · not found
- hood. — .hood name service ag.hood/name-service · alive
- ai.aivonic/mcp · alive
- BAMF.ai ai.bamf/bamf · not MCP
- Chronary ai.chronary/mcp · alive
- Name.ai MCP Server ai.name/nameai-mcp · alive
- RadiusOS CRM ai.radiusos.www/crm · 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-16, 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.