tabellum-mcp@0.1.2
VERIFIED· startup onlyPublisher claims: "MCP bridge to the Tabellum database client: schema, reads, SQL drafts; writes approved in the app." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Started and answered initialize; the tool list did not come back (tools/list error: Tabellum is not running (no /tmp/ks-detonate-thQcVl/task/home/.tabellum/mcp.json). Start the desktop app, then try again.). Authenticated tool behavior not tested.- Tested
- server startup over stdio · MCP initialize · every file read, file written and host contacted by what ran
- Not tested
- the tool list · what the tools do when called with a real credential
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- no credential files read · no network
- What we could not test
- the tool list · what the tools do when called with a real credential
Connect it under the guard. Started and answered initialize; the tool list did not come back (tools/list error: Tabellum is not running (no /tmp/ks-detonate-thQcVl/task/home/.tabellum/mcp.json). Start the desktop app, then try again.). Authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; started and answered initialize; the tool list did not come back (tools/list error: Tabellum is not running (no /tmp/ks-detonate-thQcVl/task/home/.tabellum/mcp.json). Start the desktop app, then try again.). Authenticated tool behavior not tested) on 2026-11-20 and scored it 92/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 25 s · 2 scenarios · 0 deviationsStatic findings
* `npx -y @dudko.dev/tabellum-mcp`: read where the running app listens, thenFix: Pin versions and sources; vendor anything fetched at install time.No other findings across 861 lines in 12 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.