Totem (mmnto) MCP Server
@mmnto/totem
npm
v1.104.0
Source verified
Published by mmnto-ai — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −22 | Hardcoded AWS access key id in server code MTC-SRC-008 | exfiltration |
| −15.4 | Dynamic evaluation of a non-literal value MTC-SRC-010 | injection |
Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
Findings 20
high Reads a sensitive credential path or dumps the environment (dist/ingest/file-resolver.js)MTC-SRC-006
In the server's implementation (`dist/ingest/file-resolver.js:73`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ~/.ssh
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/ingest/file-resolver.js
high Hardcoded AWS access key id in server code (dist/sanitize.test.js)MTC-SRC-008
A live-looking AWS access key id is hardcoded in `dist/sanitize.test.js:181`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: AWS access key id: AKIA…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server dist/sanitize.test.js
high Dynamic evaluation of a non-literal value (dist/semgrep-adapter.js)MTC-SRC-010
In the server's implementation (`dist/semgrep-adapter.js:66`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/semgrep-adapter.js
high Dynamic code execution in server code (dist/pipeline-observation.test.js)MTC-SRC-001
In the server's implementation (`dist/pipeline-observation.test.js:170`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/pipeline-observation.test.js
high Dynamic code execution in server code (dist/retired-lessons.test.js)MTC-SRC-001
In the server's implementation (`dist/retired-lessons.test.js:27`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/retired-lessons.test.js
high Dynamic code execution in server code (dist/rule-tester.test.js)MTC-SRC-001
In the server's implementation (`dist/rule-tester.test.js:8`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/rule-tester.test.js
high Dynamic code execution in server code (dist/semgrep-adapter.js)MTC-SRC-001
In the server's implementation (`dist/semgrep-adapter.js:66`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/semgrep-adapter.js
high Dynamic code execution in server code (dist/semgrep-adapter.test.js)MTC-SRC-001
In the server's implementation (`dist/semgrep-adapter.test.js:9`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/semgrep-adapter.test.js
high Dynamic code execution in server code (dist/spine/windtunnel-firing.test.js)MTC-SRC-001
In the server's implementation (`dist/spine/windtunnel-firing.test.js:20`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: eval(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/spine/windtunnel-firing.test.js
high Shell/command execution in server code (dist/ast-query.js)MTC-SRC-002
In the server's implementation (`dist/ast-query.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/ast-query.js
high Shell/command execution in server code (dist/compile-lesson.test.js)MTC-SRC-002
In the server's implementation (`dist/compile-lesson.test.js:2333`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawn(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/compile-lesson.test.js
high Shell/command execution in server code (dist/compiler.test.js)MTC-SRC-002
In the server's implementation (`dist/compiler.test.js:1173`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawn(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/compiler.test.js
high Shell/command execution in server code (dist/packaged-exports.test.js)MTC-SRC-002
In the server's implementation (`dist/packaged-exports.test.js:45`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawnSync(
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/packaged-exports.test.js
high Shell/command execution in server code (dist/parity-detect.test.js)MTC-SRC-002
In the server's implementation (`dist/parity-detect.test.js:905`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/parity-detect.test.js
high Shell/command execution in server code (dist/sys/exec.d.ts)MTC-SRC-002
In the server's implementation (`dist/sys/exec.d.ts:18`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/sys/exec.d.ts
high Shell/command execution in server code (dist/sys/exec.js)MTC-SRC-002
In the server's implementation (`dist/sys/exec.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/sys/exec.js
high Shell/command execution in server code (dist/sys/git.js)MTC-SRC-002
In the server's implementation (`dist/sys/git.js:111`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: spawn (
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/sys/git.js
high Shell/command execution in server code (dist/sys/helpers.js)MTC-SRC-002
In the server's implementation (`dist/sys/helpers.js:12`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/sys/helpers.js
medium Dynamic module load from a non-literal (dist/ast-grep-wasm-shim.test.js)MTC-SRC-005
In the server's implementation (`dist/ast-grep-wasm-shim.test.js:19`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: import(shimPath)
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/ast-grep-wasm-shim.test.js
medium Dynamic module load from a non-literal (dist/pack-discovery.js)MTC-SRC-005
In the server's implementation (`dist/pack-discovery.js:272`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: require(resolvedPath)
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/pack-discovery.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.104.0 latest |
D 63/100 | 20 | 1.5.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @mmnto/totem --onlineOther implementations of Totem 2
Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →
Security scan results for the Totem (HuzuTech) MCP server.
Security scan results for the Totem (thebriangao) MCP server.
More in Learning & Documentation
Security scan results for the Ab Integrations MCP server.
Security scan results for the Academic Research MCP server.
Security scan results for the Academic Research Mcp Suite MCP server.
Security scan results for the Adonis Docs MCP server.
Security scan results for the Adonis Mcp Docs MCP server.
Security scan results for the Advisor MCP server.