vertica-mcp@0.1.4
VERIFIED· not startedPublisher 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.
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_UNAUTHORIZEDor--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.
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 deviationsStatic findings
assert os.path.exists(".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.with open(".env", "r") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.logging.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.with open(".env", "w") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Create .env configuration file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load .env firstFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.with open(".env", "r") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.It 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.with open(".env", "w") as f:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if os.path.exists(".env"):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_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.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
Not checked against OSV yet; the weekly check has not reached this version.