Skills/PyPI/verdictswarm-mcp

verdictswarm-mcp@0.2.1

VERIFIED· not started

Publisher claims: "Every tool has an answer — your agent needs a decision. MCP server for the VerdictSwarm pre-trade check: a machine-readable avoid/caution/clear before your agent trades, plus intended-size exit feasibility and holder-cluster attribution on Solana." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher sentien-labs · publishing for 110 daysInstalls 93Last detonated 49 min ago
$claude mcp add verdictswarm-mcp -- uvx verdictswarm-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
VS_API_KEYConfiguration, not credentials: SOLANA_RPC_URL, VS_API_URL, VS_CONFIG_DIR, VS_MCP_SERVICE_KEY, VS_PAYMENT_WALLET, VS_TIMEOUT, VS_TRANSPORT
Where it talks to
no vendor host named in the codeAlso vswarm.io, solana.com — not the publisher's domain; check what for before connecting.
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, and read the third-party hosts first. The code names vswarm.io, solana.com as well as its own vendor. The guard injects VS_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx verdictswarm-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-20 and scored it 93/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.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

No findings across 2,724 lines in 27 files.

Cost to the agent

Instructions loaded
≈100 tok
1 file · 27 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

Not checked against OSV yet; the weekly check has not reached this version.