teradata-mcp-server@0.2.8
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
AUTH_CACHE_TTLAUTH_MODEAUTH_RATE_LIMIT_ATTEMPTSAUTH_RATE_LIMIT_WINDOWCHAT_API_KEYDSA_PASSWORDTD_PATConfiguration, not credentials: CONFIG_DIR, DATABASE_URI, DEFAULT_ROW_LIMIT, DSA_BASE_URL, DSA_CONNECTION_TIMEOUT, DSA_HOST, DSA_PORT, DSA_PROTOCOL, DSA_USERNAME, DSA_VERIFY_SSL, HOOKS_MODULE, LOG_DIR, LOGGING_LEVEL, LOGMECH, MAX_ROW_LIMIT, MCP_HOST, MCP_PATH, MCP_PING_INTERVAL, MCP_PORT, MCP_TRANSPORT, NO_FILE_LOGS, PROFILE, PROGRESSIVE_DISCLOSURE, REGISTRY_REFRESH_INTERVAL, TD_BASE_URL, TD_MAX_OVERFLOW, TD_PEM, TD_POOL_SIZE, TD_POOL_TIMEOUT, XDG_STATE_HOME- Where it talks to
- no vendor host named in the codeAlso private-td-url.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 private-td-url.com as well as its own vendor. The guard injects AUTH_CACHE_TTL, AUTH_MODE, AUTH_RATE_LIMIT_ATTEMPTS, AUTH_RATE_LIMIT_WINDOW, CHAT_API_KEY, DSA_PASSWORD, TD_PAT 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-19 and scored it 88/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
spec.loader.exec_module(mod) # type: ignore[union-attr]Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.exec(func_str, globals())Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.return eval(type_hint, {"__builtins__": {}}, namespace)Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.mod = importlib.util.module_from_spec(spec)Fix: 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.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 teradata-mcp-server@0.2.8 as of 10 h ago. This is the package itself, not its dependencies.