Mindswap MCP Server
mindswap
npm
v3.3.0
Published by shiporbleed — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Your AI's black box recorder. Auto-track project state so any AI tool picks up where the last one stopped.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 11 = 89. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −11 | Untrusted input concatenated into a command sink ×3 MTC-SRC-009 | injection |
2. Client adoption risk — 89 − 7 = 82. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 a deduction.
Findings 9
high Shell/command execution in server code (src/build-test.js)MTC-SRC-002
In the server's implementation (`src/build-test.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: { execSync } = require('child_process'); const fs = require('fs'); const path = require('path'); /** * Detect build/te
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 src/build-test.js
high Shell/command execution in server code (src/git.js)MTC-SRC-002
In the server's implementation (`src/git.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: { execSync } = require('child_process'); const path = require('path'); const fs = require('fs'); const GIT_TIMEOUT = 15
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 src/git.js
high Shell/command execution in server code (src/pr.js)MTC-SRC-002
In the server's implementation (`src/pr.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: { execSync } = require('child_process'); const chalk = require('chalk'); const { readState, getDataDir, getHistory } = r
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 src/pr.js
high Shell/command execution in server code (src/state.js)MTC-SRC-002
In the server's implementation (`src/state.js:64`): 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: { execSync } = require('child_process'); return execSync('git branch --show-current', { cwd: projectRoot, stdi
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 src/state.js
high Shell/command execution in server code (src/switch.js)MTC-SRC-002
In the server's implementation (`src/switch.js:4`): 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: { execSync } = require('child_process'); const { save } = require('./save'); const { generate } = require('./generate');
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 src/switch.js
high Shell/command execution in server code (src/team.js)MTC-SRC-002
In the server's implementation (`src/team.js:3`): 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: { execSync } = require('child_process'); function isTeamMode(projectRoot) { return readTeamConfig(projectRoot).enable
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 src/team.js
medium Untrusted input concatenated into a command sink (src/pr.js)MTC-SRC-009
In the server's implementation (`src/pr.js:178`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: newBody, 'utf-8'); execSync(`gh pr edit ${pr.number} --body-file "${tmpFile}"`, { cwd: projectRoot, stdio: 'p
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 src/pr.js
medium Untrusted input concatenated into a command sink (src/switch.js)MTC-SRC-009
In the server's implementation (`src/switch.js:234`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: }...`); try { exec(`${tool.openCmd} ${tool.openArg}`, { cwd: projectRoot, stdio: 'pipe',
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 src/switch.js
medium Untrusted input concatenated into a command sink (src/team.js)MTC-SRC-009
In the server's implementation (`src/team.js:69`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: y) { try { return execSync(`git config --get ${key}`, { cwd: projectRoot, encoding: 'utf-8', std
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 src/team.js
Tools 4
Each tool and what it can reach — statically extracted from the published source.
mindswap_get_contextno sensitive capabilitymindswap_memoryno sensitive capabilitymindswap_save_contextno sensitive capabilitymindswap_searchno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (4 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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 |
|---|---|---|---|---|
v3.3.0 latest |
B 82/100 | 9 | 1.13.0 | 2026-09-07 |
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 mindswap --onlineMore in AI, Memory & Reasoning
FDA device & vehicle recall risk for AI agents: recall history, MAUDE trend, risk score.
Open-source MCP server exposing Agent402.Tools' catalog — 500+ strong: 400+ self-hostable tools + 100 multi-tool skill packs (security-audit, trend-analysis, structured-scrape, decode-blob, forecasting-bake-off) for AI agents — browser, web search & answe
Zero-dependency MCP server that gives AI agents a self-updating project memory in AGENTS.md. Returns merge instructions instead of mutating state, so every change is a reviewable diff.
MCP Apps UI resources and server helpers for n8n
MCP server providing comprehensive access to BookStack knowledge management system
MCP server for tracking achievements with STAR methodology