ToolsMCP
Tabellum
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- dudko.dev
- Prerequisites
- Install @dudko.dev/tabellum-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.2 · updated
- Official links
Publisher’s description
MCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.2, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- dudko.dev
- Version observed
- 0.1.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/dev.dudko%2Ftabellum/versions/0.1.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Query a database in plain language | Publisher description mentions “database”, “sql”, “schema”. | No connection check or task run. Capability is as described by the publisher. | Rule database-query matched: “database”, “sql”, “schema”. Rule database-query. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@dudko.dev/tabellum-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
dev.dudko/tabellum
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.