rigosis-smax-mcp@0.16.0
CAUTION· not startedPublisher claims: "MCP server by Rigosis for OpenText™ Service Management (SMAX): EMS records, comments, attachments. Not an OpenText product." 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: Caution 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
SMAX_MCP_AUTH_MODESMAX_MCP_PASSWORDSMAX_MCP_PATConfiguration, not credentials: SMAX_MCP_CA_BUNDLE, SMAX_MCP_HTTP_HOST, SMAX_MCP_HTTP_PORT, SMAX_MCP_LANG, SMAX_MCP_MAX_ATTACHMENT_MB, SMAX_MCP_PAT_ACTIVE_KEY, SMAX_MCP_PAT_STORE_PATH, SMAX_MCP_PORTAL_URL, SMAX_MCP_REGISTER_NONCE_TTL, SMAX_MCP_REGISTER_SESSION_MAX, SMAX_MCP_REGWEB_REDIRECT_URI, SMAX_MCP_SYSTEM_NAME, SMAX_MCP_TRANSPORT, SMAX_MCP_USERNAME- Where it talks to
- no vendor host named in the codeAlso microsoftonline.com, microsoft.com, windows.net — 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 microsoftonline.com, microsoft.com, windows.net as well as its own vendor. The guard injects SMAX_MCP_AUTH_MODE, SMAX_MCP_PASSWORD, SMAX_MCP_PAT 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-16 and scored it 76/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Credential pass-through configuration. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
"Configuration table) or create a .env file."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Env-driven configuration. Process env wins over .env (override=False)."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.token_provider=PassthroughTokenProvider(), verify=config.verify(),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run([claude, "mcp", "get", key],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.return subprocess.run([claude, "mcp", "remove", key, "--scope", "user"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.class PassthroughTokenProvider:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(build_claude_add_args(values, uvx_path, command, target),Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""smax-mcp-verify: check that .env config actually authenticates against SMAX."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.raise ConfigError(f"Missing required env var: {name} (set it in the process env or .env)")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.flow). ``PassthroughTokenProvider`` reads that token from the SDK auth contextFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.from smax_mcp.oauth import PassthroughTokenProviderFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 rigosis-smax-mcp@0.16.0 as of 7 min ago. This is the package itself, not its dependencies.
What would make this Verified
4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim rigosis-development-team: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.