Skills/PyPI/spinqit-mcp-tools

spinqit-mcp-tools@0.0.3

VERIFIED· install only

Publisher claims: "The MCP server for SpinQ Cloud." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher spinqtech · publishing for 499 daysInstalls 67Last detonated 1 h ago
$claude mcp add spinqit-mcp-tools -- uvx spinqit-mcp-tools
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 1 of 1 bundled script 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
PRIVATEKEYPATHConfiguration, not credentials: SPINQCLOUD_HOST, SPINQCLOUDHOST, SPINQCLOUDUSERNAME
Where it talks to
no vendor host named in the codeAlso spinq.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
use of the skill by an agent

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names spinq.com as well as its own vendor. The guard injects PRIVATEKEYPATH only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx spinqit-mcp-tools

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 (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 84/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 · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.0sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: ModuleNotFoundError: No module named 'mcp'
0.1sprocess1 of 1 bundled script run with no arguments
0.1sprocessscript backend runs setup only
0.1sprocessscript backend runs setup only
0.2sprocesssecond launch, clock +45 days, CI unset
0.2sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'

Static findings

CRITICAL
README directs the reader to a committed installerREADME.md:39- Download the `mcpenv-installer-win-x86_64.bat` script from the following link:Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

No other findings across 1,433 lines in 16 files.

Cost to the agent

Instructions loaded
≈47 tok
1 file · 16 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 spinqit-mcp-tools@0.0.3 as of 48 min ago. This is the package itself, not its dependencies.