Tobilu Qmd MCP Server
@tobilu/qmd
npm
v2.8.3
Source verified
Published by tobi — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 6 = 94. 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 |
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 7
high Shell/command execution in server code (dist/cli/mcp-pid.js)MTC-SRC-002
In the server's implementation (`dist/cli/mcp-pid.js: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: ecFileSync } from "node:child_process"; /** * Pid/log filenames for the MCP HTTP daemon. * The default index keeps `mc
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/cli/mcp-pid.js
high Shell/command execution in server code (dist/cli/qmd.js)MTC-SRC-002
In the server's implementation (`dist/cli/qmd.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: wn as nodeSpawn } from "child_process"; import { isQmdMcpPid, mcpDaemonStateFiles } from "./mcp-pid.js"; import { embedL
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/cli/qmd.js
high Shell/command execution in server code (dist/cli/version.js)MTC-SRC-002
In the server's implementation (`dist/cli/version.js:15`): 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: ecFileSync } from "node:child_process"; import { readFileSync, realpathSync } from "node:fs"; import { join } from "node
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/cli/version.js
medium Dynamic module load from a non-literal (dist/ast.js)MTC-SRC-005
In the server's implementation (`dist/ast.js:112`): 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_statement) @import (import_from_statement) @import `, go: ` (type_declaration) @type (func
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.js
low Shell/command execution in packaging/dev tooling (scripts/build.mjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/build.mjs:2`): 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 } from "node:child_process"; import { chmodSync, readFileSync, realpathSync, renameSync, writeFileSync } from
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 scripts/build.mjs
low Shell/command execution in packaging/dev tooling (scripts/package-smoke.mjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/package-smoke.mjs:2`): 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 } from "node:child_process"; import { existsSync, readFileSync, statSync } from "node:fs"; import { join } fr
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 scripts/package-smoke.mjs
low Shell/command execution in packaging/dev tooling (scripts/test-all.mjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test-all.mjs:2`): 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 } from "node:child_process"; import { join } from "node:path"; import { fileURLToPath } from "node:url"; con
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 scripts/test-all.mjs
Tools 4
Each tool and what it can reach — statically extracted from the published source.
getno sensitive capabilitymulti_getno sensitive capabilityqueryno sensitive capabilitystatusno 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 2
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 |
|---|---|---|---|---|
v2.8.3 latest |
A 94/100 | 7 | 1.13.0 | 2026-09-08 |
v2.5.3 |
B 88/100 | 6 | 1.12.1 | 2026-08-16 |
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 @tobilu/qmd --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