Skills/PyPI/winnr-mcp

winnr-mcp@0.6.1

VERIFIED· not started

Publisher claims: "MCP server for the Winnr email infrastructure API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher winnr-app · publishing for 242 daysInstalls 159Last detonated 30 min ago
$claude mcp add winnr-mcp -- uvx winnr-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
WINNR_API_TOKENWINNR_CONFIRM_SECRETConfiguration, not credentials: FIREBASE_SERVICE_ACCOUNT, WINNR_API_URL, WINNR_DASHBOARD_URL, WINNR_MCP_ISSUER, WINNR_MCP_TABLE, WINNR_TIMEOUT
Where it talks to
winnr.app (its own)
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 with a scoped credential, under the guard. It asks for WINNR_API_TOKEN, WINNR_CONFIRM_SECRET and talks to winnr.app. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets WINNR_API_TOKEN=winnr.app,WINNR_CONFIRM_SECRET=winnr.app -- uvx winnr-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-21 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
Process kill commandsrc/winnr_mcp/remote/oauth.py:307 · Process kill command — agent can terminate processes# The grant is gone for good: kill the backing API token too.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Collects environment variables by secret-like namestests/test_config.py:37 · Collects environment variables by secret-like namesenv = {k: v for k, v in os.environ.items() if k != "WINNR_API_TOKEN"}Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03
MEDIUM
Python subprocess execution detectedscripts/deploy_remote.py:65 · Python subprocess execution detectedsubprocess.run([sys.executable, "-m", "pytest", "-q"], cwd=ROOT, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/deploy_remote.py:73 · Python subprocess execution detectedsubprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈362 tok
2 files · 44 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 winnr-mcp@0.6.1 as of 1 min ago. This is the package itself, not its dependencies.