Skills/PyPI/silvanexum-mcp

silvanexum-mcp@0.2.0

VERIFIED· not started

Publisher claims: "Model Context Protocol server for Silvanexum — the spend-control plane for AI agents. Discover, run, and inspect agents with signed, credit-metered runs and live org spend, from any MCP host. Run with `uvx silvanexum-mcp`." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher silvanexum · publishing for 140 daysInstalls 80Last detonated 55 min ago
$claude mcp add silvanexum-mcp -- uvx silvanexum-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
SILVANEXUM_API_KEYConfiguration, not credentials: DO_NOT_TRACK, SILVANEXUM_BASE_URL, SILVANEXUM_TELEMETRY, SILVANEXUM_WEB_URL
Where it talks to
silvanexum.com (its own)
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. It asks for SILVANEXUM_API_KEY and talks to silvanexum.com. 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 SILVANEXUM_API_KEY=silvanexum.com -- uvx silvanexum-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 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.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

No findings across 540 lines in 7 files.

Cost to the agent

Instructions loaded
≈93 tok
1 file · 7 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 silvanexum-mcp@0.2.0 as of 22 min ago. This is the package itself, not its dependencies.