Skills/npm/tm1-mcp-server

tm1-mcp-server@10.5.1

VERIFIED· startup only

Publisher 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.

Registry npm (MCP server)Publisher ffschrattenecker · publishing for 50 daysInstalls 1,781Last detonated 3d ago
$claude mcp add tm1-mcp-server -- npx -y @ffschrattenecker/tm1-mcp-server
WatchReport an issue

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_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.

$vet-skills run --net declared -- npx -y @ffschrattenecker/tm1-mcp-server

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; startup only; authenticated tool behavior not tested) on 2026-11-11 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 · 34 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
14sprocessdependency install exit 0
34sclaimedstartup only: exited (0) before answering · code: 'ERR_MODULE_NOT_FOUND', url: 'file:///tmp/ks-detonate-oOZFRx/task/home/work/acme-api/.claude/skills/tm1-mcp-server/dist/tools/metadata/resolve-default-members.js' } Node.js v22.23.4
34sprocessscript backend runs setup only
34sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/secrets-cli.js:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesmigrate <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.
AST05
HIGH
Access to sensitive file pathsdist/connections.js:53 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst 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.
AST05
HIGH
Access to sensitive file pathsdist/connections.js:35 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* `.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.
AST05
HIGH
Access to sensitive file pathsdist/secrets-cli.js:64 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesio.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.
AST05
HIGH
Access to sensitive file pathsdist/secrets.js:1 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
HIGH
Access to sensitive file pathsdist/connections.js:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
HIGH
Access to sensitive file pathsdist/config.js:164 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`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.
AST05
HIGH
Access to sensitive file pathsdist/load-env.js:4 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
HIGH
Access to sensitive file pathsdist/load-env.js:7 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// `.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.
AST05
HIGH
Access to sensitive file pathsdist/load-env.js:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// `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.
AST05
HIGH
Access to sensitive file pathsdist/connections.js:3 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
HIGH
Access to sensitive file pathsdist/secrets-cli.js:33 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst envFile = join(folder, ".env");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/connections.js:51 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files/** 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.
AST05
HIGH
Access to sensitive file pathsdist/secrets-cli.js:96 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* 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.
AST05
HIGH
Access to sensitive file pathsdist/load-env.js:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// `.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.
AST05
HIGH
Access to sensitive file pathsdist/tools/local-file.js:40 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* 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.
AST05
HIGH
Access to sensitive file pathsdist/secrets.js:3 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
HIGH
Access to sensitive file pathsdist/types.js:53 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…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.
AST05
HIGH
Access to sensitive file pathsdist/secrets.js:60 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesthrow 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.
AST05
HIGH
Access to sensitive file pathsdist/session-manager.js:45 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
MEDIUM
npx invocation of non-well-known packagedist/types.js:53 · npx invocation of non-well-known package — may execute untrusted code…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.
AST06
MEDIUM
npx invocation of non-well-known packagedist/connections.js:234 · npx invocation of non-well-known package — may execute untrusted code"`npx -y @ffschrattenecker/tm1-mcp-server secrets migrate <connection>`");Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsdist/tools/define-tool.js:99 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"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.
AST05
HIGH
Access to sensitive file pathsdist/secrets.js:61 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`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.
AST05
HIGH
Access to sensitive file pathsdist/tools/rest/shape.js:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// 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.
AST05
MEDIUM
npx invocation of non-well-known packagedist/secrets.js:122 · npx invocation of non-well-known package — may execute untrusted code`missing one with \`npx -y @ffschrattenecker/tm1-mcp-server secrets set ${connection} <KEY>\`.`);Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsdist/secrets.js:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files/** 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.
AST05
HIGH
Access to sensitive file pathsdist/tools/local-file.js:52 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files`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.
AST05

Cost to the agent

Instructions loaded
≈64 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 @ffschrattenecker/tm1-mcp-server@10.5.1 as of 3d ago. This is the package itself, not its dependencies.