Log10x MCP Server
log10x-mcp
npm
v1.15.2
Source verified
Published by log-10x — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.
Findings 14
high Reads a sensitive credential path or dumps the environment (build/lib/siem/cloudwatch.d.ts)MTC-SRC-006
In the server's implementation (`build/lib/siem/cloudwatch.d.ts:10`): 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: .aws/credentials
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 build/lib/siem/cloudwatch.d.ts
high Reads a sensitive credential path or dumps the environment (build/lib/siem/cloudwatch.js)MTC-SRC-006
In the server's implementation (`build/lib/siem/cloudwatch.js:10`): 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: .aws/credentials
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 build/lib/siem/cloudwatch.js
high Reads a sensitive credential path or dumps the environment (build/tools/dependency-check.js)MTC-SRC-006
In the server's implementation (`build/tools/dependency-check.js:69`): 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: .aws/credentials
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 build/tools/dependency-check.js
high Shell/command execution in server code (build/lib/action-intent-parser.js)MTC-SRC-002
In the server's implementation (`build/lib/action-intent-parser.js:137`): 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 build/lib/action-intent-parser.js
high Shell/command execution in server code (build/lib/cap-csv-fetch.js)MTC-SRC-002
In the server's implementation (`build/lib/cap-csv-fetch.js:121`): 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 build/lib/cap-csv-fetch.js
high Shell/command execution in server code (build/lib/compile-jobs.js)MTC-SRC-002
In the server's implementation (`build/lib/compile-jobs.js:33`): 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 build/lib/compile-jobs.js
high Shell/command execution in server code (build/lib/compile-runner.js)MTC-SRC-002
In the server's implementation (`build/lib/compile-runner.js:60`): 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 build/lib/compile-runner.js
high Shell/command execution in server code (build/lib/configure-engine/kubectl-writer.d.ts)MTC-SRC-002
In the server's implementation (`build/lib/configure-engine/kubectl-writer.d.ts:127`): 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 build/lib/configure-engine/kubectl-writer.d.ts
high Shell/command execution in server code (build/lib/configure-engine/kubectl-writer.js)MTC-SRC-002
In the server's implementation (`build/lib/configure-engine/kubectl-writer.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: 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 build/lib/configure-engine/kubectl-writer.js
high Shell/command execution in server code (build/lib/customer-metrics.js)MTC-SRC-002
In the server's implementation (`build/lib/customer-metrics.js:37`): 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 build/lib/customer-metrics.js
high Shell/command execution in server code (build/lib/dev-cli.js)MTC-SRC-002
In the server's implementation (`build/lib/dev-cli.js:28`): 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 build/lib/dev-cli.js
high Shell/command execution in server code (build/lib/discovery/shell.js)MTC-SRC-002
In the server's implementation (`build/lib/discovery/shell.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 build/lib/discovery/shell.js
high Shell/command execution in server code (build/lib/env-config/store-k8s.js)MTC-SRC-002
In the server's implementation (`build/lib/env-config/store-k8s.js:41`): 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 build/lib/env-config/store-k8s.js
medium Hardcoded egress to an external endpoint (build/lib/metrics-backend.js)MTC-SRC-003
In the server's implementation (`build/lib/metrics-backend.js:789`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch('https://oauth2.googleapis.com/token'
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 build/lib/metrics-backend.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.15.2 latest |
A 100/100 | 14 | 1.5.0 | 2026-07-22 |
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 log10x-mcp --onlineMore in Data Science & ML
Security scan results for the 2sio MCP server.
Security scan results for the Ab Ibge MCP server.
Security scan results for the Abgeordnetenwatch MCP server.
Security scan results for the Acta MCP server.
Security scan results for the Adapter MCP server.
Security scan results for the Addon MCP server.