Skills/PyPI/sieve-mcp

sieve-mcp@0.3.0

VERIFIED· not started

Publisher claims: "From company name to investment decision. Sieve scores startups across 7 dimensions so you know who's worth a meeting." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher lmwharton · publishing for 280 daysInstalls 106Last detonated 1 h ago
$claude mcp add sieve-mcp -- uvx sieve-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
SIEVE_API_KEYConfiguration, not credentials: SIEVE_API_URL
Where it talks to
no vendor host named in the codeAlso arceusxventures.com, posthog.com — 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 arceusxventures.com, posthog.com as well as its own vendor. The guard injects SIEVE_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx sieve-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-18 and scored it 89/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

HIGH
Stripe-like API key pattern detected.claude/settings.local.json:4 · Stripe-like API key pattern detected — possible hardcoded or harvested key{ "permissions": { "allow": [ "Bash(SIEVE_API_KEY=\"sk_live_UuEtLNHMth0xUQMI16CX06XzFc-3hP4uhAED9bf1xaU\" uv run python -c \"\nimport hashlib\nkey = ''sk_live_UuEtLNH…Fix: Never read or enumerate credential locations; accept a documented environment variable instead.
AST03

No other findings across 1,487 lines in 12 files.

Cost to the agent

Instructions loaded
≈64 tok
1 file · 12 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 sieve-mcp@0.3.0 as of 53 min ago. This is the package itself, not its dependencies.