Ai Consultation MCP Server

ai-consultation-mcp npm v2.3.1

Published by menesekinci — 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.

Trust grade
B
86/100
Last scanned get badge →
Trust
B · 86/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
B Why this grade threat 93 − adoption risk = 86/100

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 − 7.5 = 93. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 93 − 7 = 86. 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:

PointsAdoption-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 6

high Shell/command execution in server code (dist/daemon/utils/lock.js)MTC-SRC-002

In the server's implementation (`dist/daemon/utils/lock.js:5`): 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: port { execSync } from 'child_process'; const CONFIG_DIR = path.join(os.homedir(), '.ai-consultation-mcp'); const LOCK_F

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/daemon/utils/lock.js

high Shell/command execution in server code (dist/installer/detector.js)MTC-SRC-002

In the server's implementation (`dist/installer/detector.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: { execFileSync } from 'child_process'; import { SUPPORTED_TOOLS } from './tools.js'; /** * Get current platform */ ex

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/installer/detector.js

high Shell/command execution in server code (dist/proxy/daemon-client.js)MTC-SRC-002

In the server's implementation (`dist/proxy/daemon-client.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: import { spawn } from 'child_process'; import path from 'path'; import fs from 'fs'; import os from 'os'; import { file

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/proxy/daemon-client.js

high Shell/command execution in server code (dist/utils/portKiller.js)MTC-SRC-002

In the server's implementation (`dist/utils/portKiller.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: port { execFile } from 'child_process'; import { promisify } from 'util'; const execFileAsync = promisify(execFile); /**

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/utils/portKiller.js

medium Untrusted input concatenated into a command sink (dist/daemon/utils/lock.js)MTC-SRC-009

In the server's implementation (`dist/daemon/utils/lock.js:24`): 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: x') { cmd = execSync(`ps -p ${pid} -o command=`, { encoding: 'utf-8' }); } else if (platform

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/daemon/utils/lock.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"ai-consultation-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: chmod +x scripts/postinstall.sh && bash scripts/postinstall.sh

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package ai-consultation-mcp

Tools 14

Each tool and what it can reach — statically extracted from the published source.

  • rag_upload_filesnetwork egress
  • consult_agentno sensitive capability
  • continue_conversationno sensitive capability
  • end_conversationno sensitive capability
  • rag_add_memoryno sensitive capability
  • rag_bulk_delete_documentsno sensitive capability
  • rag_bulk_update_foldersno sensitive capability
  • rag_delete_documentno sensitive capability
  • rag_get_doc_chunksno sensitive capability
  • rag_list_docsno sensitive capability
Show 4 more tools ↓
  • rag_list_foldersno sensitive capability
  • rag_list_memoriesno sensitive capability
  • rag_searchno sensitive capability
  • rag_update_doc_folderno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v2.3.1 latest B 86/100 6 1.9.0 2026-07-23

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.

MCP Trust Score: B · 86/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ai-consultation-mcp/badge.svg)](https://mcptrustchecker.com/registry/ai-consultation-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/ai-consultation-mcp"><img src="https://mcptrustchecker.com/registry/ai-consultation-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ai-consultation-mcp/badge.json via https://img.shields.io/endpoint?url=…

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 ai-consultation-mcp --online

Use the free API → How scoring works

More in Developer Tools