mseep-teradata-mcp-server@0.1.4
VERIFIED· not startedPublisher claims: "Model Context Protocol (MCP) server for Teradata, Community edition" 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
TD_PATConfiguration, not credentials: DATABASE_URI, LOG_DIR, LOGGING_LEVEL, LOGMECH, MCP_HOST, MCP_PATH, MCP_PORT, MCP_TRANSPORT, NO_FILE_LOGS, PROFILE, TD_BASE_URL, TD_MAX_OVERFLOW, TD_PEM, TD_POOL_SIZE, TD_POOL_TIMEOUT, VS_NAME, XDG_STATE_HOME- 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 TD_PAT 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-12 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
kill $SERVER_PIDFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# It uses the connection URL from the environment variable DATABASE_URI from a .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.--debug Enable debug mode with verbose loggingFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct." teradata-mcp-server --mcp_transport sse --mcp_host 127.0.0.1 --mcp_port 8001\n"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.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 mseep-teradata-mcp-server@0.1.4 as of 43 h ago. This is the package itself, not its dependencies.