Skills/npm/jupiterone-mcp

jupiterone-mcp@2.9.3

VERIFIED· not started

Publisher 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.

Registry npm (MCP server)Publisher jupiterone · publishing for 535 daysInstalls 3,721Last detonated 3d ago
$claude mcp add jupiterone-mcp -- npx -y @jupiterone/jupiterone-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
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 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 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.

$vet-skills run --secrets JUPITERONE_API_KEY=jupiterone.io,JUPITERONE_OAUTH_TOKEN=jupiterone.io,USERLESS_TOKEN=jupiterone.io -- npx -y @jupiterone/jupiterone-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-11 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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
12sprocessdependency install exit 1 · npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /tmp/ks-detonate-JYWT2C/task/home/.npm/_logs/2026-11-11T22_36_09_877Z-debug-0.log
12sclaimednot started: dependency install failed (exit 1); the server itself was not observed
12sprocessscript backend runs setup only
12sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagepackage.json:12 · npx invocation of non-well-known package — may execute untrusted code"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.
AST06
MEDIUM
npx invocation of non-well-known packagedist/utils/usage.js:20 · npx invocation of non-well-known package — may execute untrusted codenpx @jupiterone/jupiterone-mcp Start the MCP server on stdioFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/utils/usage.js:22 · npx invocation of non-well-known package — may execute untrusted codenpx @jupiterone/jupiterone-mcp --version Print the versionFix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathspackage.json:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"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.
AST05
MEDIUM
npx invocation of non-well-known packagepackage.json:13 · npx invocation of non-well-known package — may execute untrusted code"inspector": "npx dotenv -e .env -- npx @modelcontextprotocol/inspector node dist/index.js",Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/utils/usage.js:21 · npx invocation of non-well-known package — may execute untrusted codenpx @jupiterone/jupiterone-mcp --help Show this helpFix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈59 tok
1 file · 81 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 @jupiterone/jupiterone-mcp@2.9.3 as of 3d ago. This is the package itself, not its dependencies.