github analyzed d0d6858

OpsMaxx/opsmaxx-mcp

SSH, files, containers and databases via the OpsMaxx desktop app - scoped per capability, audited.

Drift inferred · capture-to-capture

No drift recorded — single capability capture; advisories appear once its surface changes.

capabilities 0 tools

transport stdio · http verified reported listed in the official MCP registry counts 0 tools · 0 res · 0 prompts permission surface via code analysis

No tools enumerated yet for this server.

code evidence vHEAD · github-tarball

evidence-backed findings quoted directly from the published source artifact — not inferred

code files: 5

fs OpsMaxx-opsmaxx-mcp-d0d6858/src/session.js :3 import { readFileSync } from 'node:fs'

shell (weak) OpsMaxx-opsmaxx-mcp-d0d6858/test/negative.test.js :1 import { spawn } from 'node:child_process'
shell (weak) OpsMaxx-opsmaxx-mcp-d0d6858/test/relay.test.js :3 import { spawn } from 'node:child_process'

net (weak) OpsMaxx-opsmaxx-mcp-d0d6858/test/stub-server.js :3 import { createServer } from 'node:http'

secrets OpsMaxx-opsmaxx-mcp-d0d6858/src/index.js :52 const session = resolveSession({ agentKey: process.env.OPSMAXX_AGENT_KEY })
secrets OpsMaxx-opsmaxx-mcp-d0d6858/src/session.js :46 const token = process.env.OPSMAXX_MCP_TOKEN
secrets (weak) OpsMaxx-opsmaxx-mcp-d0d6858/test/stub-server.js :5 const TOKEN = process.env.STUB_TOKEN