jupiterone-mcp@2.9.5
VERIFIED· not startedPublisher claims: "Model Context Protocol server for JupiterOne account rules and rule details" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
JUPITERONE_API_KEYJUPITERONE_OAUTH_TOKENUSERLESS_TOKENConfiguration, not credentials: JUPITERONE_ACCOUNT_ID, JUPITERONE_BASE_URL, JUPITERONE_SKIP_QUERY_VALIDATION- Where it talks to
- jupiterone.io, jupiterone.com (its own)
- 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. It asks for JUPITERONE_API_KEY, JUPITERONE_OAUTH_TOKEN, USERLESS_TOKEN and talks to jupiterone.io, jupiterone.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.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 2.9.3
vet-skills diff jupiterone-mcp 2.9.3 2.9.5In the sandbox, this version reached for nothing 2.9.3 did not. Compared from the two recorded runs, not from source.
2.9.3 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
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; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 88/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 · 12 s · 2 scenarios · 0 deviationsStatic findings
npx @jupiterone/jupiterone-mcp --help Show this helpFix: Pin versions and sources; vendor anything fetched at install time."inspector": "npx dotenv -e .env -- npx @modelcontextprotocol/inspector node dist/index.js",Fix: Pin versions and sources; vendor anything fetched at install time."inspector": "npx dotenv -e .env -- npx @modelcontextprotocol/inspector node dist/index.js",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx @jupiterone/jupiterone-mcp --version Print the versionFix: Pin versions and sources; vendor anything fetched at install time.npx @jupiterone/jupiterone-mcp Start the MCP server on stdioFix: Pin versions and sources; vendor anything fetched at install time."dev": "npm run build && npx nodemon --watch src --ext ts --ignore src/generated --exec 'npm run build'",Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
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 @jupiterone/jupiterone-mcp@2.9.5 as of 8 h ago. This is the package itself, not its dependencies.