Docxtpl MCP Server
docxtpl-mcp
npm
v0.5.0
Published by yourusername — 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.
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. 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 3
high Shell/command execution in server code (bin/index.js)MTC-SRC-002
In the server's implementation (`bin/index.js: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: pawn, spawnSync } from 'child_process'; import { fileURLToPath } from 'url'; import { dirname, join } from 'path'; impor
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 bin/index.js
low Shell/command execution in packaging/dev tooling (scripts/install.cjs)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/install.cjs: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'); console.log('📦 Settin
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/install.cjs
low Package runs install-time scripts (postinstall)MTC-SUP-010
"docxtpl-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/install.cjs
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package docxtpl-mcp
Tools 14
Each tool and what it can reach — statically extracted from the published source.
delete_documentno sensitive capabilityextract_text_from_documentno sensitive capabilitygenerate_documentno sensitive capabilitygenerate_sample_datano sensitive capabilityget_document_metadatano sensitive capabilityget_template_schemano sensitive capabilitylist_documentsno sensitive capabilitylist_templatesno sensitive capabilityparse_docx_documentno sensitive capabilityparse_excel_documentno sensitive capability
Show 4 more tools ↓
parse_pdf_documentno sensitive capabilityparse_ppt_documentno sensitive capabilitypreview_templateno sensitive capabilityvalidate_templateno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (14 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 |
|---|---|---|---|---|
v0.5.0 latest |
A 92/100 | 3 | 1.9.0 | 2026-07-24 |
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 docxtpl-mcp --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.