Skills/PyPI/wistx-mcp

wistx-mcp@1.0.71

VERIFIED· not started

Publisher claims: "WISTX MCP Server - DevOps compliance and pricing context for coding agents" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher wistx · publishing for 373 daysInstalls 190Last detonated 1 h ago
$claude mcp add wistx-mcp -- uvx wistx-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
GEMINI_API_KEYGITHUB_TOKENREDIS_PASSWORDWISTX_API_KEYConfiguration, not credentials: MEMORYSTORE_ENABLED, MEMORYSTORE_HOST, MEMORYSTORE_PORT, PYTHONPATH, PYTHONWARNINGS, REDIS_URL, WISTX_API_URL
Where it talks to
wistx.ai (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 GEMINI_API_KEY, GITHUB_TOKEN, REDIS_PASSWORD, WISTX_API_KEY and talks to wistx.ai. 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 GEMINI_API_KEY=wistx.ai,GITHUB_TOKEN=wistx.ai,REDIS_PASSWORD=wistx.ai,WISTX_API_KEY=wistx.ai -- uvx wistx-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-21 and scored it 81/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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsapi/config.py:3 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesAll settings are loaded from environment variables (.env file).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/validate_auth_onboarding_e2e.py:77 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesresult.fail("SECRET_KEY is still using default value. Please update SECRET_KEY in .env file.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:37 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Check if .env file existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsrun_mcp_local.sh:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho " - .env file should be configured"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/validate_auth_onboarding_e2e.py:80 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesresult.fail(f"SECRET_KEY is too short ({secret_key_length} chars, need 32+). Please update SECRET_KEY in .env file.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsapi/config.py:27 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesAll settings are loaded from environment variables (.env file).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsrun_mcp_local.sh:17 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ ! -f ".env" ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsapi/config.py:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesExample .env file:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsrun_mcp_local.sh:18 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "⚠️ Warning: .env file not found"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsapi/config.py:28 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesThe .env file should be in the project root directory.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsapi/config.py:4 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesRequired variables must be set in .env file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsstart_server.sh:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "Please copy env.example to .env and configure it"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:38 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ -f "$PROJECT_ROOT/.env" ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
Dynamic module loadingscripts/test_embeddings.py:24 · Dynamic module loadingcompliance_models = importlib.util.module_from_spec(spec)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedscripts/generate_docs.py:15 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Destructive file system command detectedDockerfile:9 · Destructive file system command detected&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Access to sensitive file pathsstart_server.sh:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "❌ Error: .env file not found"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File permission modification commandDockerfile:28 · File permission modification command — agent changes file ownership/permissionsRUN chmod +x api/start.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:41 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "⚠️ .env file not found - create it with required variables"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsstart_server.sh:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ ! -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:63 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho " 💡 No credentials needed - MCP server reads from .env automatically!"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
Dynamic module loadingscripts/test_embeddings.py:25 · Dynamic module loading (importlib.loader.exec_module via provenance)spec.loader.exec_module(compliance_models)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Access to sensitive file pathswistx_mcp/config.py:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:39 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "✅ .env file found"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈54 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 wistx-mcp@1.0.71 as of 47 min ago. This is the package itself, not its dependencies.