stackless-mcp@1.0.0b9
VERIFIED· install onlyPublisher claims: "Local MCP server exposing Stackless app APIs to terminal agents" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 6 of 6 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
STACKLESS_AUTH_STORAGESTACKLESS_TOKENConfiguration, not credentials: STACKLESS_BASE_URL, STACKLESS_COOKIE, STACKLESS_MCP_RUN_ID, STACKLESS_TIMEOUT_SECONDS, STACKLESS_TOOLSETS- 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 with a scoped credential, under the guard. It asks for STACKLESS_AUTH_STORAGE, STACKLESS_TOKEN and talks to its vendor. 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.
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; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 91/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 · 1 s · 2 scenarios · 0 deviationsStatic findings
`revision` (write it into `stackless.json` before the next upload), theFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.No other findings across 7,033 lines in 13 files.
Cost to the agent
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 stackless-mcp@1.0.0b9 as of 6 h ago. This is the package itself, not its dependencies.