dev.dudko/tabellum
Tabellum
Is the Tabellum MCP server down? Yes. It has given no valid answer since 2026-10-19: not MCP.
MCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app.
not MCP down since 2026-10-19 · probed 2026-11-14 · unchanged since 2026-10-26
MCP error -32603: Tabellum is not running (no /root/.tabellum/mcp.json). Start the desktop app, then try again.
- Run it
- npx -y @dudko.dev/tabellum-mcp@0.1.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- tabellum 0.1.2
- Capabilities
- resources, tools
- Repository
- https://github.com/dudko-dev/tabellum-mcp-setup
- Website
- https://tabellum.dudko.dev
- Registry
- active, updated 2026-10-25 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- dev.ctxfile/ctxfile · crashed on start
- ASOLens dev.danielhan.asolens/mcp · alive
- Drengr dev.drengr/server · crashed on start
- Baton dev.dudko/baton · crashed on start
- dev.dungbeetle/mcp · alive
- Extract Insurance dev.extractinsurance/extract-insurance · alive
- dev.ezstat/ezstat-mcp-server · alive
- dev.fentz.envcp/envcp · crashed on start
Servers that mention approved or database.
- Aevia ai.aeviamodeler/aevia · needs auth
- ai.argushq/enforcement-database · no DNS
- ai.docuwriter/docuwriter · needs auth
- ai.duvera/gateway · alive
- EOSL.ai — Hardware End-of-Life Database ai.eosl/eosl · alive
- Foliora Managed AI Search ai.foliora/search · needs auth
- JustDeploy ai.justdeploy/mcp · needs auth
- ai.kanonik/kanonik · 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-19, in every probe since then.
- The endpoint answers HTTP 200, but not with a valid MCP initialize result. Common causes: the URL is a web page or a REST API and not the MCP endpoint, the server answers a JSON-RPC error on initialize, or the response is HTML.