mseep-jenkins-mcp-enterprise@1.0.4
VERIFIED· not startedPublisher claims: "MCP server for Jenkins integration with AI assistants, providing build management, log analysis, and failure diagnostics." 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
JENKINS_TOKENConfiguration, not credentials: CACHE_COMPRESSION, CACHE_DIR, CACHE_MAX_SIZE_MB, CACHE_RETENTION_DAYS, CHUNK_OVERLAP, CHUNK_SIZE, CLEANUP_INTERVAL_HOURS, CLEANUP_RETENTION_DAYS, DISABLE_VECTOR_SEARCH, EMBEDDING_MODEL, JENKINS_MCP_DIAGNOSTIC_CONFIG, JENKINS_MCP_LOG_FILE, JENKINS_MCP_LOG_LEVEL, JENKINS_TIMEOUT, JENKINS_URL, JENKINS_USER, JENKINS_VERIFY_SSL, LOG_FILE, MAX_CONCURRENT_CLEANUPS, MCP_TRANSPORT, QDRANT_HOST, UVICORN_HOST, UVICORN_PORT, VECTOR_COLLECTION_NAME, VECTOR_TIMEOUT- Where it talks to
- no vendor host named in the codeAlso jenkins.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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names jenkins.com as well as its own vendor. The guard injects JENKINS_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
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-12 and scored it 93/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 deviationsStatic findings
result = subprocess.run(cmd, capture_output=True, text=True, timeout=30)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(cmd, capture_output=True, text=True, timeout=30)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 mseep-jenkins-mcp-enterprise@1.0.4 as of 2d ago. This is the package itself, not its dependencies.