Skills/npm/tenantshield-mcp

tenantshield-mcp@0.2.3

VERIFIED· not started

Publisher claims: "> Model Context Protocol (MCP) server for PostgreSQL and Supabase Row-Level Security verification." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher tensorjetai · publishing for 12 daysInstalls 900Last detonated 1 h ago
$claude mcp add tenantshield-mcp -- npx -y tenantshield-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

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
server startup · the tool list · tool behavior

Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y tenantshield-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 0.2.2

vet-skills diff tenantshield-mcp 0.2.2 0.2.3

In the sandbox, this version reached for nothing 0.2.2 did not. Compared from the two recorded runs, not from source.

0.2.2 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 90/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 · 2 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
1.7sprocessdependency install exit 1 · npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /tmp/ks-detonate-3SfNnJ/task/home/.npm/_logs/2026-11-20T00_42_56_628Z-debug-0.log
1.7sclaimednot started: dependency install failed (exit 1); the server itself was not observed
1.7sprocessscript backend runs setup only
1.7sprocessno install scripts to re-run

Static findings

No findings across 3,837 lines in 5 files.

Cost to the agent

Instructions loaded
≈62 tok
1 file · 5 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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

No advisories in OSV for tenantshield-mcp@0.2.3 as of 28 min ago. This is the package itself, not its dependencies.