Tabellum
NPM · @DUDKO.DEV/TABELLUM-MCP · SCANNED SEP 27
MCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
- Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 4 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Tabellum MCP server?
Tabellum runs locally as an npm package, launched with npx -y @dudko.dev/tabellum-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @dudko.dev/tabellum-mcp
claude mcp add dev-dudko-tabellum -- npx -y @dudko.dev/tabellum-mcp
{
"mcpServers": {
"dev-dudko-tabellum": {
"command": "npx",
"args": [
"-y",
"@dudko.dev/tabellum-mcp"
]
}
}
} {
"servers": {
"dev-dudko-tabellum": {
"command": "npx",
"args": [
"-y",
"@dudko.dev/tabellum-mcp"
]
}
}
} codex mcp add dev-dudko-tabellum -- npx -y @dudko.dev/tabellum-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-dudko-tabellum": {
"type": "local",
"command": [
"npx",
"-y",
"@dudko.dev/tabellum-mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-dudko-tabellum --command npx --arg -y --arg @dudko.dev/tabellum-mcp
mcp_servers:
dev-dudko-tabellum:
command: "npx"
args: ["-y", "@dudko.dev/tabellum-mcp"] {
"McpServers": {
"dev-dudko-tabellum": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@dudko.dev/tabellum-mcp"
]
}
}
} assistant mcp add dev-dudko-tabellum -t stdio -c npx -a -y @dudko.dev/tabellum-mcp
{
"mcpServers": {
"dev-dudko-tabellum": {
"command": "npx",
"args": [
"-y",
"@dudko.dev/tabellum-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 40
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Analysed npm/@dudko.dev/tabellum-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
The sandbox run completed and this package exposed no tools.
What is the Tabellum MCP server?
Tabellum is an MCP server listed in the public MCP registry as dev.dudko/tabellum. MCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app. This page covers its npm package (@dudko.dev/tabellum-mcp).
Is the Tabellum MCP server safe to use?
Tabellum scores 40 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tabellum MCP server expose?
Tabellum exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.
Is the Tabellum MCP server still maintained?
Tabellum is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.