Skills/PyPI/steampunk-spotter-mcp

steampunk-spotter-mcp@6.7.0

VERIFIED· install only

Publisher claims: "MCP server for Steampunk Spotter: Lets AI agents verify Ansible and Terraform code against your policies." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher xlab-d.o.o.-pypi · publishing for 14 daysInstalls 445Last detonated 5 h ago
$claude mcp add steampunk-spotter-mcp -- uvx steampunk-spotter-mcp
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
3 of 3 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

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
no credential variables read in the code
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- uvx steampunk-spotter-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 6.7.0a9

vet-skills diff steampunk-spotter-mcp 6.7.0a9 6.7.0

In the sandbox, this version reached for nothing 6.7.0a9 did not. Compared from the two recorded runs, not from source.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 90/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.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ModuleNotFoundError: No module named 'pydantic'
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ModuleNotFoundError: No module named 'mcp'
0.2sprocess3 of 3 bundled scripts run with no arguments
0.2sprocessscript backend runs setup only
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

No findings across 621 lines in 5 files.

Cost to the agent

Instructions loaded
≈67 tok
1 file · 5 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

No advisories in OSV for steampunk-spotter-mcp@6.7.0 as of 4 h ago. This is the package itself, not its dependencies.