teradata-mcp-server (teradata/teradata-mcp-server) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Emerging
74/100
13 days ago

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

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

teradata

Source: modelscope

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 2 credentials: DSA_PASSWORD, CHAT_API_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.
configCONFIG_DIR
configPROFILE
configDSA_BASE_URL
configDSA_HOST
configDSA_PORT
configTD_BASE_URL
configAUTH_RATE_LIMIT_ATTEMPTS
configAUTH_RATE_LIMIT_WINDOW
configDATABASE_URI"": "teradata://<USERNAME>:<PASSWORD>@<HOST_URL>:1025/<USERNAME>"
configLOGMECH
configTD_POOL_SIZE
configTD_MAX_OVERFLOW
configTD_POOL_TIMEOUT
configDSA_PROTOCOL
configDSA_USERNAME
🔐 secretDSA_PASSWORD
configDSA_VERIFY_SSL
configDSA_CONNECTION_TIMEOUT
configDEFAULT_ROW_LIMITRow Limit Protection — Configurable caps (, MAX_ROW_LIMIT) prevent LLM token overflow
configMAX_ROW_LIMITRow Limit Protection — Configurable caps (DEFAULT_ROW_LIMIT, ) prevent LLM token overflow
🔐 secretCHAT_API_KEY
configTD_PAT
configTD_PEM
configLOG_LEVEL
configXDG_STATE_HOME
configLOG_DIR
configNO_FILE_LOGS
configLOGGING_LEVEL
configMCP_TRANSPORT
configMCP_HOST
configMCP_PORT
configMCP_PATH
configMCP_PING_INTERVAL
configAUTH_MODE
configAUTH_CACHE_TTL
configPROGRESSIVE_DISCLOSURE
configHOOKS_MODULE
// 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

2/2 tools missing one or more hints — search_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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 test coverage

Only 0/2 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

2 child_process/subprocess calls in production code — runs shell commands (src/teradata_mcp_server/app.py:320, src/teradata_mcp_server/utils.py:199)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

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 5 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/teradata-teradata-mcp-server-1pci74)](https://m8ven.ai/mcp/teradata-teradata-mcp-server-1pci74)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 2d43b32cf693e8cb4e6ca070ddee47002587afca
code hash: 08f9bf5f21fb173e505cef0780773dee21657ad0831c5211036721df12290f37
verified: 8/13/2026, 10:15:26 PM
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