io.github.joosthel/sevdesk-mcp
io.github.joosthel/sevdesk-mcp
Is the io.github.joosthel/sevdesk-mcp MCP server down? No. It is up and needs env, probed 2026-10-30.
Complete sevDesk MCP server: all API endpoints, guarded writes, built-in bookkeeping audits.
needs env probed 2026-11-15 · unchanged since 2026-10-30
MCP error -32000: Connection closed SEVDESK_READ_ONLY must be one of 1/true/yes/on or 0/false/no/off (got 'mcpcost-placeholder').
- Run it
- npx -y sevdesk-mcp@0.5.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/joosthel/sevdesk-mcp
- Registry
- active, updated 2026-10-20 · registry entry
- Changes
- 2 recorded, reachable in 1 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 npmjs.com, the ones next to this name; all of them.
- io.github.jonfishr/tronbyt-mcp · needs env
- io.github.jongall45/frontrun-mcp-server · alive
- io.github.jonybur-oc/mcp-server · alive
- io.github.jonybur/mcp-server · alive
- Tree-sitter MCP Server io.github.joowani/tree-sitter-mcp-server · alive
- io.github.jordanburke/dokploy-mcp-server · alive
- io.github.jordanburke/joplin-mcp-server · needs env
- io.github.jordanburke/microsoft-todo-mcp-server · alive
Servers that mention sevdesk.
- sevdesk MCP by usefulapi io.usefulapi/sevdesk · timeout
- io.github.makririch/buchpilot · alive
- sevdesk MCP Server and API by Cotlet dev.cotlet/sevdesk · not probed
- sevDesk io.github.jaylann/mcp-server-sevdesk · alive
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-23 06:52 | needs env | ||||
| 2026-10-16 06:26 | alive | 241 ms | 23 | 7.7k | 4.1k |
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 exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.