tm1-mcp-server@11.0.0
VERIFIED· startup onlyPublisher claims: "Personal testing fork of flameY3T1/tm1-mcp-server (npm: tm1-mcp-server). Use the original." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
SECRET_KEYSTM1_ACCESS_TOKENTM1_ALLOW_UNMASKED_SECRETSTM1_API_KEYTM1_AUTH_MODETM1_CLIENT_SECRETTM1_MCP_HTTP_TOKENTM1_PASSWORDTM1_SECRETSTM1_SSL_REJECT_UNAUTHORIZEDConfiguration, not credentials: DOTENV_CONFIG_PATH, TM1_ALLOW_PROD_WRITES, TM1_BASE_URL, TM1_CAM_PASSPORT, TM1_CLIENT_ID, TM1_CONNECTIONS, TM1_CONNECTIONS_DIR, TM1_DATABASE, TM1_ENVIRONMENT, TM1_IAM_URL, TM1_INSTANCE, TM1_KEEP_ALIVE_INTERVAL, TM1_LOG_FILE, TM1_LOG_LEVEL, TM1_MAX_RESPONSE_CHARS, TM1_MCP_HTTP_ALLOWED_ORIGINS, TM1_MCP_HTTP_HOST, TM1_MCP_HTTP_PORT, TM1_MCP_TRANSPORT, TM1_MODE, TM1_NAMESPACE, TM1_PROXY, TM1_REQUEST_TIMEOUT, TM1_RESPONSE_MODE, TM1_SANDBOX_PREFIX, TM1_TENANT, TM1_USER, TM1_VERSION- Where it talks to
- no vendor host named in the codeAlso ibm.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names ibm.com as well as its own vendor. The guard injects SECRET_KEYS, TM1_ACCESS_TOKEN, TM1_ALLOW_UNMASKED_SECRETS, TM1_API_KEY, TM1_AUTH_MODE, TM1_CLIENT_SECRET, TM1_MCP_HTTP_TOKEN, TM1_PASSWORD, TM1_SECRETS, TM1_SSL_REJECT_UNAUTHORIZED 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.
What changed since 10.5.1
vet-skills diff tm1-mcp-server 10.5.1 11.0.0In the sandbox, this version reached for nothing 10.5.1 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-19 and scored it 84/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 · 36 s · 2 scenarios · 0 deviationsStatic findings
`Set them in your shell or .env file before starting the server.`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Each connection is a folder with a `.env` under ~/.tm1/mcp-servers/ (theFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Set TM1_MODE=readwrite in that connection's .env to allow writes.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Connection secrets kept in the OS keychain instead of the `.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`Remove ${plain.length === 1 ? "it" : "them"} from the .env ` +Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* files (TM1 credentials, `~/.ssh`) or write anywhere.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// A connection folder opts in with `TM1_SECRETS=keychain`. Its `.env` thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose./** Every `.env` key that holds a credential. */Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.migrate <connection> move the plaintext secrets of <connection>/.envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// per-connection .env cannot change it, so TM1Config.maxResponseChars is notFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."`npx -y @ffschrattenecker/tm1-mcp-server secrets migrate <connection>`");Fix: Pin versions and sources; vendor anything fetched at install time.// `.env` relative to the compiled entrypoint (dist/load-env.js -> ../.env, i.e.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// credential inputs (.env mtime, keychain secret) differ from the ones itFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const envFile = join(folder, ".env");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.throw new Error(`TM1_SECRETS=keychain, but the .env still sets ${plain.join(", ")}. ` +Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const fileEnv = parseDotenv(readFileSync(join(folder, ".env")));Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Per connection, only the folder's own `.env` decides mode and version. ModeFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `.env` sets one, instead of ignoring it silently.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…ix TM1_USER and the password: in the connection's .env, or in the OS keychain (`npx -y @ffschrattenecker/tm1-mcp-server secrets set <connection>`) when it sets TM1_SE…Fix: Pin versions and sources; vendor anything fetched at install time.// Load environment from .env BEFORE any other module evaluates. MCP clientsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`environment (MCP 'env:' block or a user environment variable, not a connection .env), ` +Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* Move the plaintext secrets of one `.env` into the keychain. Order matters:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`missing one with \`npx -y @ffschrattenecker/tm1-mcp-server secrets set ${connection} <KEY>\`.`);Fix: Pin versions and sources; vendor anything fetched at install time./** Server-level keys a connection folder's `.env` sets — all of them ignored. */Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Set TM1_MODE=readwrite in that connection's .env to allow writes outside sandboxes.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.io.out(`The .env does not set TM1_SECRETS=keychain yet, so the server ` +Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…M1 rejected the credentials. Fix TM1_USER and the password: in the connection's .env, or in the OS keychain (`npx -y @ffschrattenecker/tm1-mcp-server secrets set <c…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// `.env` — the single most common first-run failure. We additionally resolveFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// `dotenv/config` (which only reads process.cwd()/.env) would never find a repoFix: 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
Not checked against OSV yet; the weekly check has not reached this version.