Vertica MCP Server (zaboura/vertica-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Limited view
71/100
1 month ago

Vertica MCP Server

Enables AI assistants to interact with Vertica Analytics Databases for querying, schema exploration, and performance optimization through natural language. It provides enterprise-grade features like fine-grained permissions, query streaming, and secure SSL/TLS connections.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

zaboura

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: MCP_API_KEY, VERTICA_PASSWORD, VERTICA_OAUTH_TOKEN, VERTICA_SSL_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configJWT_ISSUER
configJWT_AUDIENCE
🔐 secretMCP_API_KEY
configVERTICA_QUERY_TIMEOUT600 # Query timeout in seconds
configVERTICA_MAX_RETRIES3 # Max retry attempts
configVERTICA_RETRY_DELAY0.1 # Base delay for retries
configVERTICA_CACHE_TTL300 # Cache TTL in seconds
configVERTICA_MAX_RESULT_MB100 # Max result size in MB
configVERTICA_RATE_LIMIT60 # Requests per minute
configVERTICA_HEALTH_CHECK_INTERVAL60 # Health check interval
configMCP_CORS_ORIGINS
configVERTICA_HOSTUpdate , VERTICA_USER, VERTICA_PASSWORD, etc.
configVERTICA_PORT"": "5433",
configVERTICA_DATABASEyour_database
configVERTICA_USERUpdate VERTICA_HOST, , VERTICA_PASSWORD, etc.
🔐 secretVERTICA_PASSWORDUpdate VERTICA_HOST, VERTICA_USER, , etc.
configVERTICA_CONNECTION_LIMIT
configVERTICA_SSL
configVERTICA_AUTH_MODE
🔐 secretVERTICA_OAUTH_TOKEN
configVERTICA_KERBEROS_SERVICE
configVERTICA_KERBEROS_HOST
configVERTICA_SSL_CERT
🔐 secretVERTICA_SSL_KEY
configALLOW_INSERT_OPERATION
configALLOW_UPDATE_OPERATION
configALLOW_DELETE_OPERATION
configALLOW_DDL_OPERATION
configVERTICA_LAZY_INIT1 # Delay connection until first use
configENVIRONMENT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

12/12 tools missing one or more hints — run_query_safely (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_query_paginated (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_query_stream (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

10/12 tool handlers declare input schemas (83%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/zaboura-vertica-mcp-171ehh)](https://m8ven.ai/mcp/zaboura-vertica-mcp-171ehh)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 3fb46f6efeb15c786f0f529bbceb109b20987f38
code hash: 59d3c8d33a30e31707d18665447593997ad1e6409f146463e322c6bf35cde5af
verified: 8/6/2026, 5:32:30 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client