Dot Ai MCP Server
@vfarcic/dot-ai
npm
v2.3.1
Published by @vfarcic — 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.
AI-powered development productivity platform that enhances software development workflows through intelligent automation and AI-driven assistance
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 − 7 = 93. 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 4
high Shell/command execution in server code (dist/core/git-utils.js)MTC-SRC-002
In the server's implementation (`dist/core/git-utils.js:73`): 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: mple-git")); const node_child_process_1 = require("node:child_process"); const jwt = __importStar(require("jsonwebtoken"
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/core/git-utils.js
high Shell/command execution in server code (dist/core/platform-utils.js)MTC-SRC-002
In the server's implementation (`dist/core/platform-utils.js:46`): 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: ayFromAIResponse; const child_process_1 = require("child_process"); const util_1 = require("util"); const 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 dist/core/platform-utils.js
high Shell/command execution in server code (dist/evaluation/eval-runner.js)MTC-SRC-002
In the server's implementation (`dist/evaluation/eval-runner.js:49`): 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: e("fs/promises"); const child_process_1 = require("child_process"); const util_1 = require("util"); const execAsync = (0
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/evaluation/eval-runner.js
high Shell/command execution in server code (dist/tools/generate-manifests.js)MTC-SRC-002
In the server's implementation (`dist/tools/generate-manifests.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: = require("zod"); const child_process_1 = require("child_process"); const util_1 = require("util"); const error_handling
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/tools/generate-manifests.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 7
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.3.1 latest |
A 93/100 | 4 | 1.13.0 | 2026-09-07 |
v2.3.0 |
A 93/100 | 4 | 1.13.0 | 2026-09-01 |
v2.2.2 |
A 93/100 | 4 | 1.12.1 | 2026-08-22 |
v2.2.1 |
A 93/100 | 4 | 1.12.1 | 2026-08-18 |
v2.1.0 |
A 93/100 | 4 | 1.12.1 | 2026-08-16 |
Show 2 more versions ↓
v2.0.0 |
A 93/100 | 4 | 1.12.1 | 2026-08-07 |
v1.25.0 |
A 93/100 | 5 | 1.12.1 | 2026-08-06 |
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 @vfarcic/dot-ai --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