Inkstone MCP Server
inkstone-mcp
npm
v0.1.6
Published by an unidentified publisher — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Agentic memory server with a dream cycle for decay, consolidation, and archival of memories.
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 |
|---|---|---|
| −12.9 | Untrusted input concatenated into a command sink ×6 MTC-SRC-009 | injection |
| −6.3 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
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 17
high Shell/command execution in server code (dist/llm/client.js)MTC-SRC-002
In the server's implementation (`dist/llm/client.js:7`): 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/llm/client.js
high Shell/command execution in server code (dist/nightly/pipeline.js)MTC-SRC-002
In the server's implementation (`dist/nightly/pipeline.js:8`): 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/nightly/pipeline.js
high Shell/command execution in server code (dist/nlm/client.js)MTC-SRC-002
In the server's implementation (`dist/nlm/client.js:7`): 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/nlm/client.js
high Shell/command execution in server code (dist/setup.js)MTC-SRC-002
In the server's implementation (`dist/setup.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/setup.js
high Shell/command execution in server code (src/llm/client.ts)MTC-SRC-002
In the server's implementation (`src/llm/client.ts:8`): 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 src/llm/client.ts
high Shell/command execution in server code (src/nightly/pipeline.ts)MTC-SRC-002
In the server's implementation (`src/nightly/pipeline.ts:9`): 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 src/nightly/pipeline.ts
high Shell/command execution in server code (src/nlm/client.ts)MTC-SRC-002
In the server's implementation (`src/nlm/client.ts:8`): 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 src/nlm/client.ts
high Shell/command execution in server code (src/setup.ts)MTC-SRC-002
In the server's implementation (`src/setup.ts: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 src/setup.ts
high Shell/command execution in server code (src/types/sql.js.d.ts)MTC-SRC-002
In the server's implementation (`src/types/sql.js.d.ts: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: exec(
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/types/sql.js.d.ts
medium Untrusted input concatenated into a command sink (dist/db/fts.js)MTC-SRC-009
In the server's implementation (`dist/db/fts.js:138`): 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: exec(`
CREATE TABLE IF NOT EXISTS ${
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/db/fts.js
medium Untrusted input concatenated into a command sink (dist/db/schema.js)MTC-SRC-009
In the server's implementation (`dist/db/schema.js:272`): 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: exec(`ALTER TABLE chunks ADD COLUMN ${col} ${
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/db/schema.js
medium Untrusted input concatenated into a command sink (dist/setup.js)MTC-SRC-009
In the server's implementation (`dist/setup.js:33`): 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: execSync(`ollama pull ${
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/setup.js
medium Untrusted input concatenated into a command sink (src/db/fts.ts)MTC-SRC-009
In the server's implementation (`src/db/fts.ts:123`): 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: exec(`
CREATE TABLE IF NOT EXISTS ${
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/db/fts.ts
medium Untrusted input concatenated into a command sink (src/db/schema.ts)MTC-SRC-009
In the server's implementation (`src/db/schema.ts:295`): 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: exec(`ALTER TABLE chunks ADD COLUMN ${col} ${
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/db/schema.ts
medium Untrusted input concatenated into a command sink (src/setup.ts)MTC-SRC-009
In the server's implementation (`src/setup.ts:38`): 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: execSync(`ollama pull ${
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/setup.ts
medium Package runs install-time scripts (postinstall)MTC-SUP-010
"inkstone-mcp" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package inkstone-mcp
low Package has no source repositoryMTC-SUP-011
"inkstone-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package inkstone-mcp
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 |
|---|---|---|---|---|
v0.1.6 latest |
C 79/100 | 17 | 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 inkstone-mcp --onlineMore in AI, Memory & Reasoning
Security scan results for the 402md MCP server.
Security scan results for the Acheron MCP server.
Security scan results for the Adaptive Recall MCP server.
Security scan results for the Agent Memory MCP server.
Security scan results for the Agent Memory MCP server.
Security scan results for the Agent Memory MCP server.