Skills/PyPI/sakshi-mcp

sakshi-mcp@0.2.1

VERIFIED· not started

Publisher claims: "Sakshi governance as an MCP server: witness, enforce, and check regulatory readiness from any MCP-capable agent — no SDK integration required." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher rotavision · publishing for 120 daysInstalls 72Last detonated 1 h ago
$claude mcp add sakshi-mcp -- uvx sakshi-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
SAKSHI_API_KEYSAKSHI_MCP_API_KEYConfiguration, not credentials: SAKSHI_API_URL, SAKSHI_MCP_BLOCK_POISONED, SAKSHI_MCP_BLOCK_STYLE, SAKSHI_MCP_CONFIDENCE_FIELDS, SAKSHI_MCP_ENFORCE, SAKSHI_MCP_EXEMPT_TOOLS, SAKSHI_MCP_FAILCLOSED_STAKES, SAKSHI_MCP_STAKES_FIELDS, SAKSHI_MCP_TIMEOUT_S, SAKSHI_MCP_TRANSPORT
Where it talks to
no vendor host named in the codeAlso tools.example — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names tools.example as well as its own vendor. The guard injects SAKSHI_API_KEY, SAKSHI_MCP_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx sakshi-mcp

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; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 88/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 · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedtests/test_http.py:45 · Python subprocess execution detectedserver = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/sakshi_mcp/proxy.py:31 · npx invocation of non-well-known package — may execute untrusted code# e.g. sakshi-mcp-proxy --agent-id abc -- npx -y @modelcontextprotocol/server-filesystem /dataFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
Process kill commandsrc/sakshi_mcp/server.py:40 · Process kill command — agent can terminate processeskill switch or safe-mode is active — must not execute). Honour `allowed`:Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

Cost to the agent

Instructions loaded
≈71 tok
1 file · 17 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 sakshi-mcp@0.2.1 as of 51 min ago. This is the package itself, not its dependencies.