mcp-vertica@0.1.14
VERIFIED· not startedPublisher claims: "A Model Context Protocol (MCP) server for Vertica database with connection pooling, schema management, and security features" 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
VERTICA_PASSWORDVERTICA_SSL_REJECT_UNAUTHORIZEDor--ssl-reject-unauthorizedConfiguration, not credentials: ALLOW_DDL_OPERATION, ALLOW_DELETE_OPERATION, ALLOW_INSERT_OPERATION, ALLOW_UPDATE_OPERATION, TRANSPORT, VERTICA_CONNECTION_LIMIT, VERTICA_DATABASE, VERTICA_HOST, VERTICA_PORT, VERTICA_SSL, VERTICA_USER- Where it talks to
- no vendor host named in the code
- 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. It asks for VERTICA_PASSWORD, VERTICA_SSL_REJECT_UNAUTHORIZED and talks to its vendor. 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.
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-10 and scored it 87/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
# 3. .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load environment variables from file if specified, otherwise try default .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."--env-file", type=click.Path(exists=True, dir_okay=False), help="Path to .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN chmod +x /app/entrypoint.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.logging.debug("Attempting to load environment from default .env file")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
No advisories in OSV for mcp-vertica@0.1.14 as of 4d ago. This is the package itself, not its dependencies.