Skills/PyPI/vertica-mcp

vertica-mcp@0.1.4

VERIFIED· not started

Publisher claims: "Production-ready MCP server for Vertica—secure tools, row streaming, pagination, and system metrics for LLM agents (Claude, Cursor, VS Code)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher zaboura · publishing for 208 daysInstalls 74Last detonated 48 min ago
$claude mcp add vertica-mcp -- uvx vertica-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
MCP_API_KEYVERTICA_AUTH_MODEVERTICA_OAUTH_TOKENVERTICA_PASSWORDVERTICA_SSL_REJECT_UNAUTHORIZED or --ssl-reject-unauthorizedConfiguration, not credentials: ALLOW_DDL_OPERATION, ALLOW_DELETE_OPERATION, ALLOW_INSERT_OPERATION, ALLOW_UPDATE_OPERATION, ENVIRONMENT, JWT_AUDIENCE, JWT_ISSUER, MCP_CORS_ORIGINS, VERTICA_CACHE_TTL, VERTICA_CONNECTION_LIMIT, VERTICA_DATABASE, VERTICA_HEALTH_CHECK_INTERVAL, VERTICA_HOST, VERTICA_KERBEROS_HOST, VERTICA_KERBEROS_SERVICE, VERTICA_LAZY_INIT, VERTICA_MAX_RESULT_MB, VERTICA_MAX_RETRIES, VERTICA_PORT, VERTICA_QUERY_TIMEOUT, VERTICA_RATE_LIMIT, VERTICA_RETRY_DELAY, VERTICA_SSL, VERTICA_SSL_CERT, VERTICA_SSL_KEY, VERTICA_USER
Where it talks to
no vendor host named in the codeAlso app1.com, app2.com — not the publisher's domain; check what for before connecting.
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, and read the third-party hosts first. The code names app1.com, app2.com as well as its own vendor. The guard injects MCP_API_KEY, VERTICA_AUTH_MODE, VERTICA_OAUTH_TOKEN, VERTICA_PASSWORD, VERTICA_SSL_REJECT_UNAUTHORIZED only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx vertica-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-20 and scored it 86/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.2sprocessdependency install exit 1 ·
0.2sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.2sprocessscript backend runs setup only
0.2sprocessno install scripts to re-run

Static findings

MEDIUM
Access to sensitive file pathstests/test_cli.py:66 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesassert os.path.exists(".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_cli.py:67 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith open(".env", "r") as f: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 pathsvertica_mcp/cli.py:70 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslogging.debug("Loading environment from default .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_cli.py:73 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith open(".env", "w") as f: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 pathsvertica_mcp/cli.py:117 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Create .env configuration 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 pathsvertica_mcp/cli.py:65 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env firstFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_cli.py:79 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith open(".env", "r") as f: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 pathsvertica_mcp/cli.py:17 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesIt supports loading environment variables from a .env file, setting up logging,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/test_cli.py:85 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswith open(".env", "w") as f: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 pathsvertica_mcp/cli.py:155 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif os.path.exists(".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 pathsvertica_mcp/server.py:448 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_path = os.path.abspath(os.path.join(module_dir, ".env"))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
≈71 tok
1 file · 32 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

Not checked against OSV yet; the weekly check has not reached this version.